why2 reasons
mandatedestination_not_allowed
op 0 pays GDFEAXQB644QNDLNVHM54KIHRPN6EOGFI62NBMMNXRHSQ6QBWDRIWMZJ, which is not in the allowlist
counterpartycounterparty_denied
GDFEAXQB644QNDLNVHM54KIHRPN6EOGFI62NBMMNXRHSQ6QBWDRIWMZJ 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
- 7b68607a574858eaa3e95e5a8d2d1eabbfd130aca24f140c409e155215ae3297
- request
- bb10df9f23f14f2a12bf0e64aee474e7c225f8f0535a3acff8ae71040fb51a6e
- transaction
- 9ecbc9f4b44584389ac5d80109b037f800a8c0a8b0850550f8432cd3ba9f17aacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 147
the chainentry 147
- sealed to the entry before
- 959c406a0456a97c5edf9ecbd9b27d007120889561fd312371d562653c0d621b
- this leaf
- 4f7f27e75360992be79195c32cc978a06fa576f73170b19a15ac1ba558f67f8b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mm75qEvXPgj13gaciSn71b/QQTGdJDpK9VBxF9BN5eLx0qRSeJ0iAyBdYc7H1fOrJvvZ9SjaBcGaqMhp0JT/CA==