why2 reasons
mandatedestination_not_allowed
op 0 pays GDBYSG7HYGE3IEKZM5VQJRCI46BJORHYWDHOP3DXP2WUF4LUNRUK5FVP, which is not in the allowlist
counterpartycounterparty_denied
GDBYSG7HYGE3IEKZM5VQJRCI46BJORHYWDHOP3DXP2WUF4LUNRUK5FVP 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
- 5c9c9e473dfea966112923506c514e1bc265a4c8457e124059b63d5f9d495273
- request
- ece11ce73b307a4ac0011968741f1fdbbd0be6465510a9a082ae8deb12bb49ff
- transaction
- 9a4a471f51ba549875b1cb69f5bdb31d1300dc7148c02dd3ee7dcfc480c8b1c4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36905
the chainentry 36905
- sealed to the entry before
- 594a66d104a0b03259e5fd3ee5d52f8416790fa27062466155fa137024f3af6f
- this leaf
- 55cd21cf0ed69cc633a7789675c021659f20f0125a69ce9a68285075f7cca465
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- O1qw5GJeWk5sUerogz/grq32eS4xdlhtXXhEGmT5hyiznMAze/Ua2Oxcta8nsHx4Bo5wx5I4iAp1TKV209q/Ag==