why2 reasons
mandatedestination_not_allowed
op 0 pays GDKZRXLMLF23LLUQHLMDEQQZQWZT4NQ443HISES5N6NFEY4DYJWAMTMZ, which is not in the allowlist
counterpartycounterparty_denied
GDKZRXLMLF23LLUQHLMDEQQZQWZT4NQ443HISES5N6NFEY4DYJWAMTMZ 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
- b7ba9324861d1aeb02244627a55a1d854d5c9cf582a72a286af6d5d1eebe74b5
- request
- 26978df9e7f57ffad11eb5b08a53b3cef7c6ac1b2a6267d39fdfc44d33dddc5f
- transaction
- 8bc5233c46ee39d4f1f51bb70c5a45150f7b94defe5598e56ea3e86eed01235ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38105
the chainentry 38105
- sealed to the entry before
- 40dca3255919eb8fc82cb7c13ce9cbf43c798c7eac44dc1331f10d347aa5d23b
- this leaf
- 7754f071785a00ce55466c2396c9296514685b81be2b4184112f42f89127b44b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7Ns6lpaISM9HqdW9DyQmXwCQz3KWhTvfX05C5NoYu6FnvAAtOYXOO5DuKGp8lwWzJeyzk4Vg8SNmiWk3gEMXAQ==