why2 reasons
mandatedestination_not_allowed
op 0 pays GAMQM22JYRYDAEZYBC7ERC6MZ2PSMWUKCSMCKYZFXKF2FQ7YUSHVGEUP, which is not in the allowlist
counterpartycounterparty_denied
GAMQM22JYRYDAEZYBC7ERC6MZ2PSMWUKCSMCKYZFXKF2FQ7YUSHVGEUP 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
- d2e8eea7be4469f336ccffa8f5e68ac3e46de3bcd7b58f3093d93de8faa8798c
- request
- a1164254ab78e6795dbb917f30b8c17bba0d5f92fb968e7147f6842c3fa84136
- transaction
- 9a3b416aa9adeaf79439234ecf8f331f3f9f8e5ffcf341cd60819d78e12801e1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35045
the chainentry 35045
- sealed to the entry before
- 4f645c588c288511f7aecb94e7d133f08f5ea5954be710a5faf2bc7a8ddeddd1
- this leaf
- 9b19dd91e742c398692ef310aef0f689e2049e72f904155d433c96a7504f25d8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eCD1S0BoWdeAhLwnFdwedv9jleexN7IbYVzHwbW0GTyZGS9z62KGZB2G1isNu4K+2ft96xsVgwzRKgaE2bAKAw==