why2 reasons
mandatedestination_not_allowed
op 0 pays GDTM4K7CP4O25DXQ5GIO4JAVPI3CCQIUV4R2SHQLELQS2QAJBZPAMKXX, which is not in the allowlist
counterpartycounterparty_denied
GDTM4K7CP4O25DXQ5GIO4JAVPI3CCQIUV4R2SHQLELQS2QAJBZPAMKXX 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
- 340c4959b63e7a1cae5ce3c798980a7d42395afe1499ca8c3484da9aea6078f8
- request
- b3d46b107916eb407ef5290e59a55989d3ab872c131f658b6926ef0000154021
- transaction
- d5c7413e6e7ee33f058abc93ca44483f7c0828343525970b8fe067a4380178bfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6954
the chainentry 6954
- sealed to the entry before
- 05a0d72b7a3bb2639cdefa229068a75fcfc582cf3a06999863ddc5280fe61402
- this leaf
- df02fa30c6511dbdd627a9ab3a067972e1c186ff91f7ec6c49bd554015635908
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Vs9WAKCZXZHgJR0E5BokvUT2gPyPdZKs2qyjitGgNQ3LVrpXGfrZ2hyN+1c56lXyg8VMjQPfWlbNMCsJT4F2Ag==