why2 reasons
mandatedestination_not_allowed
op 0 pays GD3WLEW5JF63JKS4U6LO7AKCKOKZVBOBMW2NEU5FJ45HYUGFEUPMG4I6, which is not in the allowlist
counterpartycounterparty_denied
GD3WLEW5JF63JKS4U6LO7AKCKOKZVBOBMW2NEU5FJ45HYUGFEUPMG4I6 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
- ec7af864dfc2d30c30c16ca5d64872661ec9f76b5f2195c12acc12802f91890f
- request
- b8c49fe061cfff0defcc2529597761e83538970a51e214139326e180b15328e7
- transaction
- f0db26da8985a368c374b833412f4dcc4b2035eb99a782c1715954ebeff16f49computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54051
the chainentry 54051
- sealed to the entry before
- c890af113a1dc2b2f1f8d0a896b94fe69b880005db4f28bd19f9c204f042d7c0
- this leaf
- 8f8afa77a19461936a5dff0b3e55afc37b0807222329d11d30785ab937457d3b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hgRWML0/P0PvmmD5qErLoWbZlc76XY5Ql3/meJVsTfJdE3ydG9eBl2gwmf/F6sWEU8JCFnF+XdMGqNPEpoMVCA==