why2 reasons
mandatedestination_not_allowed
op 0 pays GDPV6URKPN2WV6RCW5AWNBPFQPOTYC43V3GMFHEHFIFZ5U5RJ5IQGLFD, which is not in the allowlist
counterpartycounterparty_denied
GDPV6URKPN2WV6RCW5AWNBPFQPOTYC43V3GMFHEHFIFZ5U5RJ5IQGLFD is on the screening list: you placed this account on the screening list for this run
what it was decided fromfingerprints
- rule compiled from it
- 98893ef9a70a10b72b2c87430244dce849651c71daa1c64d3e5e85f4553d61be
- request
- f4cfb7175c6a366437b2a39ae38e9aa309c65a5f25292069dd822ff9efaf69cf
- transaction
- be917593c2407def8fb1376216b5661035e38570a59419e4deb8a112eb109e31computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3548
the chainentry 3548
- sealed to the entry before
- e3cabc700d8a7e63acb90e53ee252a43e3d73df94aa6b8bf8f997dd879ad1b21
- this leaf
- 02977d57b3a99d1ffeb2ab45c3d1cc9493664793137687a6e5424a96241fbd9d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aIWY/GMiAlxdydcCnjahANO5JwKCFO8nBpZqZcUSxkITfc9drLOkFm4gOerryrnCyn9tktH4W38Y1o6buSWeCA==