why2 reasons
mandatedestination_not_allowed
op 0 pays GDJENP5TYOAESAPWQ2IXJZ2SRDJ6JPUDJPAW7EU6J3TQ5HJ7NZMVEX33, which is not in the allowlist
counterpartycounterparty_denied
GDJENP5TYOAESAPWQ2IXJZ2SRDJ6JPUDJPAW7EU6J3TQ5HJ7NZMVEX33 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
- 3cd83c812f5a15ebc13d9610c8205113c4824272e3cfc6972a5922edef3f5e9b
- request
- 9751a4444abadc92b9a7d2ddcfe8b17c24e4e68ee71e22937a9268686684958a
- transaction
- b10d68fa671a9dae8b2f465b99e10f92c279668b8ad330977ceefd9c4b975f53computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41992
the chainentry 41992
- sealed to the entry before
- d93d29c5e9abb19f00d040333c0ce7ff4cafde7caa2a4666dd5260da1ee71390
- this leaf
- 8a9b6955c40f5307e3199644ed367460122ceff13c376412fa46aa6a2374ada9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TMTD59odbSV2dcixxCsVF70F+JRKYP0PajV+LW2+oizZPIYyFoupyHVRvhEZ6+sxDxvl50dzZ4cBgC+f8r2vAw==