why2 reasons
mandatedestination_not_allowed
op 0 pays GCVFDBXDUGTUYEEGUWGXPZ3BQHADVWJ5XNMY3SD3NDMN5EANHVGYEOF3, which is not in the allowlist
counterpartycounterparty_denied
GCVFDBXDUGTUYEEGUWGXPZ3BQHADVWJ5XNMY3SD3NDMN5EANHVGYEOF3 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
- 00af9deb3badcaf7c2054f8a4eac0121ebcd9ac93aaed3d19fdb42c5746aaf9f
- request
- 837312aac4568207efa415ad796af4db6b52f584d27065ca0d08c308edddd16e
- transaction
- 0205139e6dca76dd519b801a60e2127e9ba7521d2f45e6a4747e3890a3183754computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47917
the chainentry 47917
- sealed to the entry before
- c0513242cd3d3542790b74c6133e90f5c246906d02b51e03dbdca2ad4505a8f4
- this leaf
- 167c07b309fde98a76cb05f9b11bba92876285519c78ecccfaa6624c4f1b2fb9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KZEbeiznwRnvTMu/nOByZC92wxzZL2q7nxbHHEnfj3MuMoAXxuOkkVGjQdEmLnA4fCboeCdwozmktIT6mGi2DA==