why2 reasons
mandatedestination_not_allowed
op 0 pays GDWY3M6WOL5WY47V5JUOD3AFWBZJTB24CY3E5AL2FAL7IRSKHYUVAYQR, which is not in the allowlist
counterpartycounterparty_denied
GDWY3M6WOL5WY47V5JUOD3AFWBZJTB24CY3E5AL2FAL7IRSKHYUVAYQR 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
- 1a3c166776457ce3165b1dec109a5ffedc325a072b1bf62680a87e3f3fdc6203
- request
- 40f47a2384e1a0424e645fb0dd3fdbfaf5e51b2c36fc949be4d34b2e8d209dc8
- transaction
- f8d39aaea0ffd08b5d029bdeb7edc8670a142675925225be802b25e5ba9fb56acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63707
the chainentry 63707
- sealed to the entry before
- 2ae8f8f97673b22eabacde7792b41a07cbdb79f680007c8e7675bd9600821ee3
- this leaf
- f237e26a4cdc22019b6322e4fa93a8dade4d4c06cd3e7528569d05c78631544a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VeNKnUJpz1y2OO1t/txQAfK0GMeu/HNXrXY7zKKgrn0c1XnnRIHUy9VZ4YKjgJjFrOCi0iSZkuNVFSIg4IHDBQ==