why2 reasons
mandatedestination_not_allowed
op 0 pays GBDTOSVFUDHTY4GWT4ZZPNFXL7S56W2P6G5ID3EYN4IX2LSLNX62LXWH, which is not in the allowlist
counterpartycounterparty_denied
GBDTOSVFUDHTY4GWT4ZZPNFXL7S56W2P6G5ID3EYN4IX2LSLNX62LXWH 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
- a10952d508ae79a4f19fd39a09dd31a6ebe98ac13bb1e48d36109d66bbe2c30a
- request
- 0b6610032ac191878b108f132f3faf9ea92646e14b63e84bca8192cd26c9fa5d
- transaction
- b5fa7152ac651278a5aa557687cbea07651c7b4a0fd152203658aff91658d321computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67074
the chainentry 67074
- sealed to the entry before
- 1a1f29dc3d0a5cfd25a53ad2eee45323335cd3f73133c55f380c3a59f6ff7bdd
- this leaf
- 004f9f56d26d4447cfc9a28900257a2e70e20c151de58c7eeb56ef4a05a92af6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 90BO5OCKY9qCLV6tIueVyqmhvMclv3Yq+9cklcwkZH3tJMNA9D06Z/OxUu1yf/dsSXvqaNyH5hZox26ad3ZoBQ==