why2 reasons
mandatedestination_not_allowed
op 0 pays GDEXTE4EA2GO4RKNORKEVPG26OICAQ2OKS5TSSLNTL3GBPH2PJ5PEG5U, which is not in the allowlist
counterpartycounterparty_denied
GDEXTE4EA2GO4RKNORKEVPG26OICAQ2OKS5TSSLNTL3GBPH2PJ5PEG5U 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
- 08ff7a9882627a7fec15e9c1a0d80a58b3c18f67e574a29af0f21fc30e3d04f9
- request
- 439be9c7362919f82f4b065ff0c12fcea2d247da0c74ac341aedad0d2777233e
- transaction
- e374a42626804de1f3083103fee47634d53eb9ee8efd78b3a34ba903a4af6409computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69182
the chainentry 69182
- sealed to the entry before
- 68c8108c71d89adbf22008f6252e366300a4687dafebb341aac99062cff51db2
- this leaf
- 16939ee7e1d86880d66df1b344ceb6f1bfc2534af0ab45e700089d0306f1b27b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +q/4kaKdZQVL01y6hh9Z6MmN+iIfOTRafDm5JEPBg+gMdWwQSeMGc3tKHIA2fICeNuGj5frSgoYaChYJgDZ2Dw==