why2 reasons
mandatedestination_not_allowed
op 0 pays GDCHFEQFGZTM6IL4K5ON4G2WQJHR6YMIAY6BG2KRDMHM7L2QCBGP5EP2, which is not in the allowlist
counterpartycounterparty_denied
GDCHFEQFGZTM6IL4K5ON4G2WQJHR6YMIAY6BG2KRDMHM7L2QCBGP5EP2 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
- 1e45c97a6e56d9d49c9b4ad66eea18c6d5b51889f4aeb255e6870a1912ab841e
- request
- a449cd2de94c1b171efc140bcd8eb053e01493955dea484e33045c1809a03108
- transaction
- 180239a1d6fe9abe4c6c5121e19620074e25b190343146c5db2215d9d5aa83b5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28625
the chainentry 28625
- sealed to the entry before
- 4b1449e27601dc9d64dc91dd810fee30c1d7b5d798ee27ff76e0e8c9110d6a74
- this leaf
- ea312b6c15d3860391f1f8a5f0281c6226af163f432652c8ec74cc143587c1c7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Siku221NO/YvBnUemYKSFFVCxygLTaI+C4ly8TM3pWH0aL8KCU+y6znlRbclgaEom7Bcu7XM6CIck2IySPBeBA==