why2 reasons
mandatedestination_not_allowed
op 0 pays GDKKKZV5FAVQO6ZS5XJ62KSYENQQ7OXLNHXJB3ZKJDKAAHKAH5IP35LF, which is not in the allowlist
counterpartycounterparty_denied
GDKKKZV5FAVQO6ZS5XJ62KSYENQQ7OXLNHXJB3ZKJDKAAHKAH5IP35LF 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
- 2c22868547cfdb193fd30884b49c577f5dcda700403671792a90d5e1a8fdad5b
- request
- 94594e3dad7a1de4a268576a150b0e6d83d2ab36c3bbba54f708bf79631d9cfc
- transaction
- 51ef654d5aa8b1c7e52a7f5b435b0dea8a4a69bdad624a39c19716f5a401079acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76150
the chainentry 76150
- sealed to the entry before
- cacdc83d3ab060533b28d1a26f8931b94597ce8fda99043eadeb764437ea87cc
- this leaf
- c22b610605e9525556fb6cfda1a3ed56836b5ed0cfa6f195246125c4fff6075a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ipHO4KaeIAivHgCPo1RPunEnCwT588R1JeSClA2ABXbUYxswGzJsnOoVdcHjzJkIsTjgTyeIq3knzcuS8puNBQ==