why2 reasons
mandatedestination_not_allowed
op 0 pays GBTYMQOM5OCW5LCTIIPIQ3N6I3N4R6S3HXKKYJBJJ4H3VRP5QCQALFTP, which is not in the allowlist
counterpartycounterparty_denied
GBTYMQOM5OCW5LCTIIPIQ3N6I3N4R6S3HXKKYJBJJ4H3VRP5QCQALFTP 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
- 2eba58be811759c4b791ccb78d4be631f9f1048c948ebbad96cdf1e4ceda5a71
- request
- 702d5b11bb410ce2599e6762356aee6b83a6e333b7dd1ffe262a95042bfa47b6
- transaction
- 321f661d82de245913c1564df73b8b0ca80ed106dd58d178dc3eeed30b02962fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32
the chainentry 32
- sealed to the entry before
- 081de40cb1a3568d89ee49a03990b8b25fd0faef0707974de5823c2ef40446ae
- this leaf
- 35d49392c8a8ae75c826e8a1a37d8e170db4bc62b797b32f9b7b18db0b16a62b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3yXbUW0hvVQSBDEPCLjww7drcBrgNCm/POLzWyeIQ5aAqTFY/TizOmFimyG756lu5x7XSm+yvbv/Ol8Gnd5yDA==