why2 reasons
mandatedestination_not_allowed
op 0 pays GDAA65TLU2IAWUQLQWJLPOP7ABZDR5FI6VDIVVIJSSYYCXMLNAPZWGZU, which is not in the allowlist
counterpartycounterparty_denied
GDAA65TLU2IAWUQLQWJLPOP7ABZDR5FI6VDIVVIJSSYYCXMLNAPZWGZU 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
- 105fc07eac8e5b6d7a39e4ba03bb9465304f3b938532cb428d21327e4badee0a
- request
- df6d239a1898c2aabd1f7de40f4dc7f0dae58b88b267c5ede0ef6d5e75a318ae
- transaction
- 44f5b680597f1e83f09ce16dd576b83b48131d1a1a4930470a5d0ce51a37bad9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13654
the chainentry 13654
- sealed to the entry before
- 7156f75b128157d7bf3942b3adeb3d40b3896325f5a399014171a91d1cbf8a5e
- this leaf
- 7942612f1fdf788049e4c8df3359fe0b6a90e423cbdb7388ff89d9f90e556001
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EGWrs/CNEubQuLeOuUl8kHWs4za+U84aWt1l2kOBqljuthOHPrhWB1er4dRvJ8hzPW159lYjsrvlzGw7H14wCQ==