why2 reasons
mandatedestination_not_allowed
op 0 pays GDZU6ITXNB5JZWPQ6COLO4FROA6WECK2Y5CH5ATBRUFSNRLDR7X5AHQH, which is not in the allowlist
counterpartycounterparty_denied
GDZU6ITXNB5JZWPQ6COLO4FROA6WECK2Y5CH5ATBRUFSNRLDR7X5AHQH 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
- a02eb21733011020e962614ab1d9f82b3f8dbf9f6b6f1eb56fcbc26f5a4947db
- request
- 340bfa93ffd9baca1d7e4844970911350e4f9ceb855869aa0f308d129c18f58b
- transaction
- 2f85c67097248745f81fb3e35bc2fc1a1a8fb927959f73881763a7defa4533f2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3686
the chainentry 3686
- sealed to the entry before
- 996ce3f7a3e7993e134bfb11995b69ddaf35813556cac2afa693ccfaaf7ceac5
- this leaf
- 7b7174ff85e543666a9769fa7a00abeb8e30730f094244a2fe8a3a276905c655
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /uuDc6v8YPZhmFSenP39azAZ9eHqkQjreq2ylfi6q89xl8zNKExyTJB+EGq5bEExr0avJ/gCzNg4lcrjcfNwAw==