why2 reasons
mandatedestination_not_allowed
op 0 pays GDMKIX7AATDECPBDXYFUEOSNGYZSC2XIQ55SPGW3SAZ7UDB7ESSMWDHX, which is not in the allowlist
counterpartycounterparty_denied
GDMKIX7AATDECPBDXYFUEOSNGYZSC2XIQ55SPGW3SAZ7UDB7ESSMWDHX 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
- a35661a92a2877e9fdd766402e8602444abe3340a82699a30ff0013df957122b
- request
- fa2bd4b152c3318c151e354e5083ca04e55c6b2b732eaa0810d82ebdfb543a89
- transaction
- 8e1f4e345af221af9dcfa1af704f0cd861167a1befe89bcf49305187b2747e49computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41137
the chainentry 41137
- sealed to the entry before
- 9992ffbcf5c5811c847865e3adfbd16a0416c8bfed82b04ef18f7a19d3d31338
- this leaf
- c03387fb951b1de8bc92c217acbdcc13343fd57c060fe5c487245dbf0a433618
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jr3m5dtu5S6fGNAvlbKHg7XHSYgidJ7a6Hl39xCpCyCMpu/kxUHV60yAQfl1WRHfY6HctJ7kJHcVRPWAo8iDAw==