why2 reasons
mandatedestination_not_allowed
op 0 pays GCWJFVDY4TI3PLXUHCTEL2IZEU5O4GA3N4K6VHHB4A3PJKZNP3MVWWQW, which is not in the allowlist
counterpartycounterparty_denied
GCWJFVDY4TI3PLXUHCTEL2IZEU5O4GA3N4K6VHHB4A3PJKZNP3MVWWQW 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
- 237a9bb657fbce58d584d309706ca01d682c52d061ac54f9b4cbcbc616c99c74
- request
- 74aa24318efe9f8505c453a651fe6e037a1054ffdf9aaa37ed2e6807284d9f46
- transaction
- 7036d2dd74417384e27f1cce6fe067273b88c4897d3ff53e60a94ba35ea07963computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17092
the chainentry 17092
- sealed to the entry before
- 81d9c39310d35adfefea840fb080d2a896eb69e10c773250bd3975fbece62d85
- this leaf
- b3945a92e487a18b5dbbb48a088a5071cdd479d615388b9f9eb2795e009c2a73
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oFT5bpPf/WbWL9rV5CCRTm6jUOHj8BUy8dM//mnJzuGyrEcnitExmOGkyW+bT5tKQ1v8oRDuD6gctIK53C/bCA==