why2 reasons
mandatedestination_not_allowed
op 0 pays GACU5EYMIYMSZRCSI47SHVBQLNIERGTA3YDUXDLPE7IIB7Y4M7E5OCDH, which is not in the allowlist
counterpartycounterparty_denied
GACU5EYMIYMSZRCSI47SHVBQLNIERGTA3YDUXDLPE7IIB7Y4M7E5OCDH 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
- c36deeac19d556774f8c5b70610627d84b3fa946312849e9ae79ff935a131824
- request
- cff5b8fae03d9b19fbaa9759388779aa71401a648866c5aff1b7c9fc9491689c
- transaction
- f063f406032c76b8dba4af8c8c05919f13430e7c077732ca79429566d96ffff6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7270
the chainentry 7270
- sealed to the entry before
- 91f6e5ede35ec02efdbb5a839ac441bd760a31c186eee5e369af5f9b9bee5441
- this leaf
- 3d5ab26d6e72ece48f6d8e3f05588bef653f8a36d2ba168063c6bfa8e0f07371
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wRD6XjCHbyVDKJkjt6mtBs+iEhPEjhUJa6jEDi9wlRI0P2XBxIvXeOJsFNv3wdl8EyS8m5HGumQREMPlhQ5PAg==