why2 reasons
mandatedestination_not_allowed
op 0 pays GDCETJRNANBMEIPDB4NQRXZBYJB37BLMHSK6L4U6FUZFSZ7E6THBII4E, which is not in the allowlist
counterpartycounterparty_denied
GDCETJRNANBMEIPDB4NQRXZBYJB37BLMHSK6L4U6FUZFSZ7E6THBII4E 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
- bcbd519524b017290b882e1ca75d4cd56d54531eef00f710cf00eb1e34c79fac
- request
- c6e1b25ace48eefca3b0cd9212744499fd323e1b3af33e10c72ae7c9ca544f95
- transaction
- 041453cf668d4d3d97952028ac438273fff729cd4b20cb285aa3ca5aad909171computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47193
the chainentry 47193
- sealed to the entry before
- 4821b3c8ea6523134aa2375f4670fcdce12ee7bc0b22cd8788775381a555d5f6
- this leaf
- 101196adb35a6d43aece8a6b2605e8053abe30ab5f5bda049873d946e30a7751
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zpdDBrm12YbZzFRr1zBWqbug/sDRLpp1KGV9P4eyXlFLTq2+6WqpdBjrqNzVAxF3xXY0KqP8VNL/qOvc0+i0BQ==