why2 reasons
mandatedestination_not_allowed
op 0 pays GB5SLT3EWYIWI4ZXYIWE4N5JQXQ4ZZLFYHQZ7TTHVNKOWYK3Z3L6ADQL, which is not in the allowlist
counterpartycounterparty_denied
GB5SLT3EWYIWI4ZXYIWE4N5JQXQ4ZZLFYHQZ7TTHVNKOWYK3Z3L6ADQL 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
- 95384d3d669b5a8e08f2740ab80ebd668b065ae19cd1fde3f5a1e20ac4f822b1
- request
- 123fe1b302a9dd2fb0c0c5188ccc4ca04d7939a7d1bc5794448d62dde7c4bb0b
- transaction
- 897a0027443c44aa4a8b96efb06774861eece89c4f16060412498c28344da680computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43936
the chainentry 43936
- sealed to the entry before
- a50abfb4c190f4e19235fa18e305dde4fa7df952ba3d98e77f2864702da4bdee
- this leaf
- 5508c69454caf87a252baceff212ec23e1c33ab1b3804b28e91f21cf6530fc62
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gxlL00x3sUKWodjfdFHLjZZhP3rt6RopNBS2TLTCMPZ6kab8IDd2qleYpJhRkpsh0NVAQL0UA1NHCu2GtkyXDw==