why2 reasons
mandatedestination_not_allowed
op 0 pays GDQBYR3J4EYWUBW2VJJC6XDCNB5CQOSQHRMJIJR75S6GSY2GWG4LM5N7, which is not in the allowlist
counterpartycounterparty_denied
GDQBYR3J4EYWUBW2VJJC6XDCNB5CQOSQHRMJIJR75S6GSY2GWG4LM5N7 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
- 3b1078c4150b2b01af74e8ed69e8d2f963a18478dd52ec8be458ca79f0ff1854
- request
- 47bb2c58d8d6f0c52c8e339aac03341f9f7b6e4667352df85f3c8f249bbdc9e0
- transaction
- 9c6f1777524001bec10eda7a0c91b30a02129dd3a37228b3e92c32b4aaca17a7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47865
the chainentry 47865
- sealed to the entry before
- 0857e0bfc2190323435ad6466a9504ab1042c53edc7990b88020e66dc18db0f4
- this leaf
- 7652529c661fade5825e660734cee21217de2fc83fb2c4f95722d6b07482f780
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GRr9+ODG07dfGAwJAxgnFOC5vISOwdXqoKNoHx+iCUrvzmfDAIE2GHuz74zqPKKcTisASpBVnnh1O2BPUNaYCg==