why2 reasons
mandatedestination_not_allowed
op 0 pays GDPLZVM255NQQKE4GB4GQRV3SSDRR6C2L3HOQSFESTLHVJOPLXFP3X7N, which is not in the allowlist
counterpartycounterparty_denied
GDPLZVM255NQQKE4GB4GQRV3SSDRR6C2L3HOQSFESTLHVJOPLXFP3X7N 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
- 3b3fc3443654f10992e4f5d4d3ffbc4bcbb34b8ab979561e531f1074e271cc0e
- request
- 65d4b0f30d3f581b42aaef7b9b6cbaeeee019d884108f1a0bb6afb30d81654a5
- transaction
- e24f81e726e117decb78fb47af24ddd0e74d2419ef5d48954f7c574e607185fccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53684
the chainentry 53684
- sealed to the entry before
- d46dc04e17950bb8fb16cb124ef97c84189cdad3496b38b30ff585948b87f508
- this leaf
- d8d2435a15ffe2dea07516c4149a7104f2581343518caa624cfde03eee265e44
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sGd/8MC7gwc4PT2tZ2j6sr8pPwx2MohXNu/kjXaY2ucG61ckSWquLntC/ytCudTI6NF0Hm9NuV3Vc92iglvIBA==