why2 reasons
mandatedestination_not_allowed
op 0 pays GDMN4YHTFAK2KBUPO53YCVXQOCJAV7V5C2QNRX6BIYSURMA476TIYGOX, which is not in the allowlist
counterpartycounterparty_denied
GDMN4YHTFAK2KBUPO53YCVXQOCJAV7V5C2QNRX6BIYSURMA476TIYGOX 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
- 5b3e20d1d1e1ce78102ef8cb701402b2e3ae7f32c88d009465f6d58532d877db
- request
- ae69311c09f2b33bd88002cb482fafce43a8544c70b860118d9af2cedc818a6f
- transaction
- 26f749bbb34653df74e6cf7b3105293f5e12e77448b0488855d01166d5389e56computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2611
the chainentry 2611
- sealed to the entry before
- 847afd51562f2b4a42a32722621f820018fecd56f27ffcb6fbb364e67e31290b
- this leaf
- bb65d7fde972ca74e8ce4965da3b4f8a227debf8a529b0ba5c06cc85ed3ec05c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hFBFV0HjumO10MYnS9vUos8+of/feVFe5bQYp76UgnrTnkxzy+WBh34wLmauECzbXyxDkmqVoSFbWz5gSUj5Cw==