why2 reasons
mandatedestination_not_allowed
op 0 pays GD223X34HZAJLR4JKUXFYCOQ2X5M5PT2NTZ3JOUJE3IRYUVEKFNUBQUG, which is not in the allowlist
counterpartycounterparty_denied
GD223X34HZAJLR4JKUXFYCOQ2X5M5PT2NTZ3JOUJE3IRYUVEKFNUBQUG 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
- 1fb94a917578ea559b8560c8cb0e703c663f7d09fe1cdf19e990443d76af78e0
- request
- b4e3e149ff194ffda301452d1736dc11b41167e8b427c91bed9990cbf8716cb6
- transaction
- 4c2d093f6d0536fc97a342883ab988780b3f8058ef985068ac34df07e0f50ca4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65969
the chainentry 65969
- sealed to the entry before
- 1b4a03072f8fda1cb88b721028d3bf342666a69f6924a4f251be18903996d73f
- this leaf
- 45fa6325092fa65ee124c403ccd7d0f9e2142d42696de5ea1d20e4787b550502
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7hNhBVb4Uk/IhDb1btdXsZhl2WiafvZdSEWo+HkWlok3kKaCoKwKbEEq/mPt2ioohhs3PxyYoO4NDM3yPdxQAQ==