why2 reasons
mandatedestination_not_allowed
op 0 pays GDX6XQRZATPUWVP4DAJL7FM5ESDBU7PS462WEOWSLBJZYAZWY6HRAV6M, which is not in the allowlist
counterpartycounterparty_denied
GDX6XQRZATPUWVP4DAJL7FM5ESDBU7PS462WEOWSLBJZYAZWY6HRAV6M 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
- d1d0ee15451c79871b40e911f8d8fb63b666ab23866db5505ad83ff865b6db9c
- request
- 7c3721b62f14402ab9b70a79dc0b03e3ee4815bbb27929af90cadad5154803b6
- transaction
- 189471d789b9a9306da7f4c3dc1ff619a18039b247817eb3d07149112faf47efcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42372
the chainentry 42372
- sealed to the entry before
- 7a82257ed175921c49e2a07904ae623bb745823c3593f16d21786a677d84606e
- this leaf
- 5fbbcdc9e4af1035ce71c314e17159db88384aa9717a8abac2a7035ec4ce57c9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jJIzuxD9SNN+xD7IujLP5IV2Njr1zVr1vHHx9PgzcmT6xBoxUjA3M6IfgglDQkzoBRzt8NA60MOsMQIrIyfxAQ==