why2 reasons
mandatedestination_not_allowed
op 0 pays GBZEVNFMSZNKB56PQ66C463L4WX7XJUNXGGMFQXDZVOOE3EQN2YHPN2C, which is not in the allowlist
counterpartycounterparty_denied
GBZEVNFMSZNKB56PQ66C463L4WX7XJUNXGGMFQXDZVOOE3EQN2YHPN2C 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
- 0d42d34684fe2de4602b2e3bcd9753aa9abba83f3f58fed8fd915187514effd2
- request
- 7c2c0ad8bb2ec84636c92e3d079e51fd8e4e3361e8a79a69e8ab6bf2b37296a0
- transaction
- d7e8198e5629986fa2752be2af424c91178e0a7a69140a91ded9624a6e434002computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62078
the chainentry 62078
- sealed to the entry before
- 4e62b26a3015bb975dc153917c735a228d0ebe7bdaabb0aeb8c0cc677834759c
- this leaf
- f4fda996b34f01a6163136f1011047f62bba88fa85d3aa4f185ad5dfad8b530c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lurVNxwPuKJG1HYSyGolYVyqfhsx7lh1l6plOfVda21Ij78mszZaf/UAvg21Kjk9MnBZpfK+Hvdl1AGkoUSXAA==