why2 reasons
mandatedestination_not_allowed
op 0 pays GDXZBVJOEUDQ5MJPHU6BPYSRMPO4QU4RCVCU4PUJ3B45JV5KO4BZGEYU, which is not in the allowlist
counterpartycounterparty_denied
GDXZBVJOEUDQ5MJPHU6BPYSRMPO4QU4RCVCU4PUJ3B45JV5KO4BZGEYU 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
- 3c043b87c5e69487776d1449d6f9f0d27186d850c2a8c61a26b43d3f388c68c4
- request
- 02c56b9a14aa6eaac918d6c461b798734c7db0c14f9703a38226a85e188c89bb
- transaction
- e0356f232f5bfbb4aaa7ecc0d36b149a708f96fed051e5a88eaf768ca79671f6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18673
the chainentry 18673
- sealed to the entry before
- f6ef6706b560242430cd81c50274df444abf4e786cd262e3e7092978141ec732
- this leaf
- 66c76dd9b6025cc49c63cefa402d6bd5e4f8b0ce187f896805c090ea7fab413f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6UzaFT8/uH9tOgQHbGEQue5YCrdZB1w9GGUVpr2OUgOujL+hlIgJ/fd9Ek3W13YRgR25taOY8bfcroT+XLkfBw==