why2 reasons
mandatedestination_not_allowed
op 0 pays GDAARMIQNFMGFGCCDCQZX7SA6FMUVSYYA6MHQDLQRUOVA5YVWUG5NQQW, which is not in the allowlist
counterpartycounterparty_denied
GDAARMIQNFMGFGCCDCQZX7SA6FMUVSYYA6MHQDLQRUOVA5YVWUG5NQQW 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
- c5a37075deb9637ce543855c4620268b3f1473d4ed62b9b329b0f0c120ad2829
- request
- a0d1a24a3ec96fadc13558fae28d3a6558e2fad3443e7ad99199a21a33b25b20
- transaction
- 8206dcf9c538ed09e38febba102477d66e69eeafb630a8fddca246432443c806computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43767
the chainentry 43767
- sealed to the entry before
- 2d5e4d434697f355483a40ab92d6bca407995982ab84575439db83c65adfce65
- this leaf
- 89147e14bd456d99ad2c2356bccf763d814f6ddde122c34953331e038b29a2fd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gRa4+sLcDL++f5aew4aDALufYzNnBNAVo66dbQGbJbZq5zSpyx7TIYfN+Ib2aCiTs2Dcm2x72Q/aXYrFh5I5CA==