why2 reasons
mandatedestination_not_allowed
op 0 pays GCYMDSMXQF767FH4KSAGPIFBHM5LUV52TWE5MWHSY66YG2FYA5K33N2S, which is not in the allowlist
counterpartycounterparty_denied
GCYMDSMXQF767FH4KSAGPIFBHM5LUV52TWE5MWHSY66YG2FYA5K33N2S 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
- 47234fd73b7faace099933e914e9a18c110bbe0299bafbb64593ef757a87af7c
- request
- 31dc890113f79bd6a6186ace83565fcab01b5881b0fb54e6752470d103d1b43f
- transaction
- 0541b1bd71a257567d22a4f81bb90aec35335c9f79e3db6e0aa3899909ef8089computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62875
the chainentry 62875
- sealed to the entry before
- 636cf05e2f6eac6beda4146b3d182bbfb561bba570ae3f527343c438c135018d
- this leaf
- 1583bcdef2e699da822860cb04d474e073aab41e4902b255fc1ec6f263b98ced
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PElbFIAYrRn//BVoKB8Lk+P2rNUJg+/0JWfB4NevbzdwOUU9aRoBflkbvboXmHze0bCdRNZH9Ijzd5M/9MRzCQ==