why2 reasons
mandatedestination_not_allowed
op 0 pays GDAMSMY3OWGNYNUSKIXNBBQLEDMTBXNSK2IJPRKH6AB6COG7JLYJNUJZ, which is not in the allowlist
counterpartycounterparty_denied
GDAMSMY3OWGNYNUSKIXNBBQLEDMTBXNSK2IJPRKH6AB6COG7JLYJNUJZ 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
- a08d21bf185f9899f3f5cce7764d4a16a5e9cfd2dd828ab134606a4950cfe49f
- request
- cff4fd73bf0772f25d1765c866b73899e80a601cc6806e7970cfb30db4dbd71d
- transaction
- f4d35180b66a57ceead120b8757e0d03ecd2dc0928bfaa2625cf3026fa27d003computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54496
the chainentry 54496
- sealed to the entry before
- 424d4be7edd20e9f663656842be1bc640dc8421ac7a774dc3a1e337bcfe322c4
- this leaf
- aa3801dd0fc30838cdb5b8541c0c3b06416d547d930164131a5d88f88242c10d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dxbHpXMlY6YrVSupc3SS/5DAM2CZHByrfewv3SkPjFUfHgD2Iyolg01gZ/sGB+tAn6WFfBYSXsf9jdZYqQgGAQ==