why2 reasons
mandatedestination_not_allowed
op 0 pays GDBTNCS5FINAB5I7WCPIAXFAZF6U4RG36GNO2U2K3PPYZ6BLVHNNASJE, which is not in the allowlist
counterpartycounterparty_denied
GDBTNCS5FINAB5I7WCPIAXFAZF6U4RG36GNO2U2K3PPYZ6BLVHNNASJE 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
- 13e0ff4236b0ef48762ba9906217eae5bc1cdf20734c542c420ec650790d2226
- request
- b9f165304e5f14597c7bbd6731ed221bdb12f68cf399289de88077e0a84cd091
- transaction
- e720df35d5da3c0412e7ecfdbc418b9e24154d4f173c774ad0d30f663897582fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32503
the chainentry 32503
- sealed to the entry before
- a1815c79ae6cb2272ff7f41fc9ec586bdf69782692e67b05e39a6ce9470da566
- this leaf
- 552dcb79dc1fdb62205e0ff03ebb9daf1275ff8833bc0e664a0cbc139a1f0e9b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Zt9eZieISOBCdsUAG7+cq8F9Xntc10FEtLHOBo1Mp/nNgOhSpyA5l0DZDrb3ha9t0KjppY/WpJFlX4Ag4DhiAw==