why2 reasons
mandatedestination_not_allowed
op 0 pays GDDJHDH4QK336H3K7ZERB6QTCM2ZHQHHBE5EBXTMLK2E5QSR3HTIZQRD, which is not in the allowlist
counterpartycounterparty_denied
GDDJHDH4QK336H3K7ZERB6QTCM2ZHQHHBE5EBXTMLK2E5QSR3HTIZQRD 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
- e51a864e6ab524c8ecea825507e3e0175a86a869044604f0d421aed1b3cc1a03
- request
- 5231e1a5a486e7acdb978b0753165b07a5ba368be8e4e045a80b2f5c8f221a25
- transaction
- 19a7fc66ae75be3d8fff625ee113d1ae136bad7040834d49c1333cb54e537608computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 772
the chainentry 772
- sealed to the entry before
- cdc639cd67a993c5f48e098770aa470d9ec7acd332c8a5a0116a29f7de1603b7
- this leaf
- 5b0bcc69dedc02dddb988cbbc59cf9fd8502a61afaea3f80fcac67a04e6742ea
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lkeCGv9XuS6wo72SbhvcBumLyZYlmKqinULcJM+ZygrcYntHlwXQF4XIEIWiaZ6n61IBI0BiDiZALRBgFKD/DQ==