why2 reasons
mandatedestination_not_allowed
op 0 pays GD6IHRIDXCEJOMSN2JOYP6Q5H3GAZ7XTJEI7CGT3M5NUASPDJDCLQZP5, which is not in the allowlist
counterpartycounterparty_denied
GD6IHRIDXCEJOMSN2JOYP6Q5H3GAZ7XTJEI7CGT3M5NUASPDJDCLQZP5 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
- a9141cdfa83616885ea5fd93f547ca92709704ffca0a462eaf80d7c4e9c320dc
- request
- 6f7035aa3ecdd30f7df25786195662b712ff2f0403c73612fb8080db012b8258
- transaction
- 993f812734a9020d0f6c86f5ea0d8a359a015d036c926affa80baa0cc33e78fdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38882
the chainentry 38882
- sealed to the entry before
- 359c45fe1f906b3dd7922a8057ba1685b92a9b4a25f5770d4be002b3e0dd6c49
- this leaf
- e7d95e8b56ef4f05ccdab8e8bef770733db153c177f6501b3c2787821d3e06c0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RWWjkOKbSiXr+FRSHxOmLqvS+f7zYhQeYNV2h23wcp94/a32RSVIykmX/TyQ7NjdNNVYOSJvv/Zt3+FMUOE9CA==