why2 reasons
mandatedestination_not_allowed
op 0 pays GDEQ4NLJSEEFURNG2P2I25BE3JS54N7AXFI67XZTJB44TRBAY3TZZKYE, which is not in the allowlist
counterpartycounterparty_denied
GDEQ4NLJSEEFURNG2P2I25BE3JS54N7AXFI67XZTJB44TRBAY3TZZKYE 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
- ccc737c9d278f6693270b91a15bf1481049c9289811c67e353a003ba70e08600
- request
- 88d35338b2b6f0d2b7cce4c4a710eba2f79f31f411d7e3310f2b79ab04bcf515
- transaction
- f61c2adc843adb49dd229dccab3a48f8d743c3e86860eac2aabf89c2f521104dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60679
the chainentry 60679
- sealed to the entry before
- 6600a04cd682625bf02df27984cb86fa3ea1da2907860719dda4918522079f4c
- this leaf
- 1734ab681e06618512234e81e02ae2014e784aedb6cb310b7b78c56f9d14f084
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7mep5qt+9tTfbyI485U8+ga0jflsZwkJfruvURouX+2t0tWKgkto1SqgAYXpgOJi0fU3uekpi+ywn/EKuFHTBg==