why2 reasons
mandatedestination_not_allowed
op 0 pays GDEY5QKX5WGQIJKEXWJS52TI3IXOW2W2YXXTVUDDT663RTPCTJCWLJTD, which is not in the allowlist
counterpartycounterparty_denied
GDEY5QKX5WGQIJKEXWJS52TI3IXOW2W2YXXTVUDDT663RTPCTJCWLJTD 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
- e8780f9da15a153b2647f6b08bea03430083908dec312f5d0f4cd5c11783b0da
- request
- 77d7669f06844a08aefc3af3a88342422fc3dc4f09bb86ca1e5cab0e94c98ea2
- transaction
- 6c19b021731cdcbf3fe767c6b8ce7a737b2afb0755819f7bd3fae228f6374910computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37681
the chainentry 37681
- sealed to the entry before
- 62d46ebec4c452937589b4bdad37cbe4148bf2b83da60646b9879d0fef09e820
- this leaf
- 3554c7c3a04928517c9083e94afd0a93c6fe3226d778337f653fea89f1face6d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Do1CfdZOND7xeLvxydymnCaVA/J+wCW9ZsaGEtPODbWj8+qp2viW6M23qhocHKC/enEPIOVPucicjDxHbJR5BQ==