why2 reasons
mandatedestination_not_allowed
op 0 pays GASCZGDC5WQBNFSZACIZPIE4ME7DUBVQAFKZ2BBGX7EAKWLFUM777W5E, which is not in the allowlist
counterpartycounterparty_denied
GASCZGDC5WQBNFSZACIZPIE4ME7DUBVQAFKZ2BBGX7EAKWLFUM777W5E 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
- e9722fe6905f49822318f39236fb1ddddce4a78e28dd8e054d62ad24c5a6131d
- request
- e5adf4fe132082dfc4d75d06a79a34faf7afa02832383bfb8eb5bcdb17a48d9f
- transaction
- 06f5068ce237455866e92500e1d50d0215a115d85de12531b83b72c591c4ec97computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67525
the chainentry 67525
- sealed to the entry before
- d73256b5c8eb57c11c0322f96eed33b4474c0af9009f370348266108d390e3a1
- this leaf
- 222588821f46e6780614559541eedd4e5d567ef3d3b2aa0b46ef2c50bedb7d64
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- l6IHy8AFLx5Vmvxb65kEJmFQX7AbghcXFX6+NNvo+mVBhQ/nfGN0t9zWGCeKPJFgoPdvS+fexR3re/V+gM41BA==