why2 reasons
mandatedestination_not_allowed
op 0 pays GDC5ZKRVBFF5L2BJ72VQE54QC5A4GBIYK3KDNTRUWMCKBCX7OZIUVJCD, which is not in the allowlist
counterpartycounterparty_denied
GDC5ZKRVBFF5L2BJ72VQE54QC5A4GBIYK3KDNTRUWMCKBCX7OZIUVJCD 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
- 624aa1cec66b5353320bc51db3bc9d944e01027a9e1ba5edb2356eafc3d350f7
- request
- 46db294da44e01389bf84b40bd27bdeda23a5b02d9a48c25b4d7878541e3adc0
- transaction
- 6e5d6a3efcc1b73f1c140ebf22bd700ced414a8fbfe9fd148f8daeb6743e8ca0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71188
the chainentry 71188
- sealed to the entry before
- c855d8fb3807f47f722c9805da520f28bac96be4b1767cf280168678292ac470
- this leaf
- 5f89248d76f1caea9df45caf0a6c1582216eca3b16d57cccca97a31caecf648e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WlyDqSz5zwkff2LKLrjxELJwbE1fHANGnwpB7uP34PO6/Lba33Ja412MrUuDTDfoo3Gxb00bJo7lMQYJe31NCg==