why2 reasons
mandatedestination_not_allowed
op 0 pays GBJ5UUYLAUS7BK4P4QE6HW4HJRS4AVZHDWP5IQWDJXWFZTMHD3XH6AC3, which is not in the allowlist
counterpartycounterparty_denied
GBJ5UUYLAUS7BK4P4QE6HW4HJRS4AVZHDWP5IQWDJXWFZTMHD3XH6AC3 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
- cb31f76caafc15d1934b19658aff6a7d9dafcdf9ea84ee66c414fc7359fcc4f6
- request
- 9e10b2d5e024cf4ba1bccf9036fb4d1a67d7d58a5d5068ddbc0ed10aa8dd2cd7
- transaction
- 43d018aa8f30a9a070bb63c007fb9eedd93fdea1467c683e770e1cbe417022d8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25552
the chainentry 25552
- sealed to the entry before
- 346cb7071371ac28524c393367871e3af9d5839e7e9025c8d7f4d659cbb22e52
- this leaf
- 510832c7ab5f0b8cea46033304cf6ca0453256835338c3e161be7e75bfa640b2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IRIqcIkvxwH5DHTYaCjK2pipESImbXuuZibaTlDdKOH9hbyMtOXttY07NGo1bEUOhQVJtgv4mAruD7Iu74GjBQ==