why2 reasons
mandatedestination_not_allowed
op 0 pays GDUKFXAX3W2XIH7IYVYSJZQ35JA4XITIGU3MVQIOOWUWLZXG4GSGC3TW, which is not in the allowlist
counterpartycounterparty_denied
GDUKFXAX3W2XIH7IYVYSJZQ35JA4XITIGU3MVQIOOWUWLZXG4GSGC3TW 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
- 54b9137a93257364dad36e993890b13b1a16bbff28cafe84f854239202ccc0fb
- request
- 18524c82cf8bb0bda9c43de253a9a13d0739e418725df7dae03464cf4223b73e
- transaction
- bc6f6b2ba72373d09fc8b8a38b17b5fc67568332d793943e1f22949f7b1d5d47computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61356
the chainentry 61356
- sealed to the entry before
- 8d7ca8a490089c783de120b3d7adde51f9d1d17b297e011dd44148b11b05fb54
- this leaf
- adde664a825c90bb0fb7563a79e5b424235fe0748985b385e1565be0a798af3f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mZALpuTvc4b6G/nNKwDC8sjuXK5mRR0HE1O6FPW/wyXaa/7W6L2gzV9bsojVdIz4/GN+ExKAWMgwRiB/SKIEDQ==