why2 reasons
mandatedestination_not_allowed
op 0 pays GD3SO7L5NRO6IUOWAXUXTG4LZBJOBFJOHDQVOS6UNZ7JGZTOEUXL2KBF, which is not in the allowlist
counterpartycounterparty_denied
GD3SO7L5NRO6IUOWAXUXTG4LZBJOBFJOHDQVOS6UNZ7JGZTOEUXL2KBF 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
- 896ceece24aec74e3fd6a4674da603ec1630d06dcb1ff6880b3eddf1e190fe6f
- request
- 1c22b9f961d79db432dc607302ab53ce5c99f9719c7faae1042f928d8f14463b
- transaction
- 16d74a3eff31d4e9b2c159ea101f57394e63288c448f1e0ae51d614bcf2d3083computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39674
the chainentry 39674
- sealed to the entry before
- 1f8d508cc727ecd1898d5545dbaa238349fcbf026f69ec0095eec8a246b53aac
- this leaf
- d34f7d083a4cdc8533abf1de8fcb6a5ae97b7b606c83fb43905af473e95dd31a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 32ml4ixfBLHf2Ti3FUG//5lhm1340m8k/lutIwwiMwsr7r4mPJ3aY4+1oDX5o0r0E+WNSer9JqEH3FjTqgvEAg==