why2 reasons
mandatedestination_not_allowed
op 0 pays GDSFWDX3ZHOMO4S2QURXZZEWPYGUMLGXEGUS4TIZEQSIBFJINAKMEU6B, which is not in the allowlist
counterpartycounterparty_denied
GDSFWDX3ZHOMO4S2QURXZZEWPYGUMLGXEGUS4TIZEQSIBFJINAKMEU6B 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
- 9c65415920eaa2fd3f8274b66faa76a09d6f1524a5f229af0f0fc1900880792c
- request
- 1896d51791baa84a1a84ba2fcdb2cb125fec2cad632ec98c4cfdeb8e0d6aa665
- transaction
- 479cd75172a94ee898cbf20274049bf53fcd761943fa7db0d28d6556189a3bd2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38615
the chainentry 38615
- sealed to the entry before
- ec3657d5c9475aa12772ee4bef2b5d67be6115ddc2e230f00de4e13124e9dcc0
- this leaf
- f3a5c62c62c53ee5e2426bdb58745b802a807020b56e523bbe2bcfeff4245e39
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aUtX6LzZSngK5JlAmCqLMAD9pVqgAPwbHBaH+pmgX00L1S8L+CC9Y2Rll038mlY0ksCoJaSyrgTeqyeYMlltBA==