why2 reasons
mandatedestination_not_allowed
op 0 pays GDTYJ4D2PG4V5VVOEYGDQZ37XNYU4NNTYVTBU5FF4TOCSA3YFX2ZDQL3, which is not in the allowlist
counterpartycounterparty_denied
GDTYJ4D2PG4V5VVOEYGDQZ37XNYU4NNTYVTBU5FF4TOCSA3YFX2ZDQL3 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
- 86c4c9c0e9d759845ee396dea8ebc99e8419600b8d9b3420d95f86befb367797
- request
- eb5e5b525afd0de990bfdcc6586fc95724182d4e3b99fd42b5ac1d7830512613
- transaction
- 9deae1c04e7519c164e81fff7a3781fd11e01914e566158ec367d31c62d8f0a0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53642
the chainentry 53642
- sealed to the entry before
- ea8ecb66e4fec1ae3cda83c3846e82824f5eb4480e99287027c4520692d6ae88
- this leaf
- 02069f167dd48decb19cfd7455126d3f9b825645b32427ce32b5fef079d3f912
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Yik4E17NqImHNIMD5eZlFNA/ynZqR/5Gz1XUzjUb3qIqY/wLsjHN6C5FqEGiLTge7reN5ndRJ/yZEN6ETxhUDg==