why2 reasons
mandatedestination_not_allowed
op 0 pays GCK4YFSNKS4EAHAU2ZO2FZXV5VKGPLHBY4CPTBC6TDLH47YFOXVNFMZX, which is not in the allowlist
counterpartycounterparty_denied
GCK4YFSNKS4EAHAU2ZO2FZXV5VKGPLHBY4CPTBC6TDLH47YFOXVNFMZX 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
- 08e5b3549aa7459b6c0b8d96cb66c68a9850e5c2dacfff9960a1228d50a55e53
- request
- 26aebb0baa6702942e4b48a009978cedbcbe4056aed2cfb062a2774f7e24e320
- transaction
- 05833974ae5d6dcdfa19248a02bd084f128e2495794f876f41c1e84350c58918computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2256
the chainentry 2256
- sealed to the entry before
- f28211e8b3bef1a0b806385ca101631ada097fe6ea536bed171a00aaf8b70355
- this leaf
- b819459c4ef82747e993b5788be0d4ae98643774a6d0f30dfda1e87eb1c60708
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AlKB9OBPPPJkRkJ9R01CeMl6+R1YYhsZAZFV35OdnWd6AaNp9dzlqirdGBfaSyNs/Ft6/EfeQLI0cC+nfQ9xAg==