why2 reasons
mandatedestination_not_allowed
op 0 pays GDMLHUFP4ILKLSNDDM6ZTQGW6WPJ6PAUBBG2TYNF2CCIAFWW5MPHCMFL, which is not in the allowlist
counterpartycounterparty_denied
GDMLHUFP4ILKLSNDDM6ZTQGW6WPJ6PAUBBG2TYNF2CCIAFWW5MPHCMFL 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
- ad17e75fb8b84ed3017f938c56e03775792be8c058a2ee375d81c2d0cf7f83a4
- request
- eeba05cae703fa26cff9c95714d09a06efe40934cc56765ab39f894309298150
- transaction
- 8566aa5fb1b352d27751017059294639084d9c190f33e926f09823428515ec1acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36654
the chainentry 36654
- sealed to the entry before
- dbbb010823aae8269b61d9c2df0741757c53f316de98f92ec06310249d7336b0
- this leaf
- cf826ea82685f5c37f7aa26fb21078648d5029b3bed16b4b8a9e5a097305eb00
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 16DToP+ccFM2jFCu2waaNh0C3NlT0SJ/hrNCukqGz2Qv2K6uaE6kOkrIMIYsn5o/Wwn3s35i7TuuSKUFrxLlBQ==