why2 reasons
mandatedestination_not_allowed
op 0 pays GDT3YMY7HFLAZQZMXQAQCOQIIZSXHAVC3B23VQHTO4FVBGQ6CU6IGTT4, which is not in the allowlist
counterpartycounterparty_denied
GDT3YMY7HFLAZQZMXQAQCOQIIZSXHAVC3B23VQHTO4FVBGQ6CU6IGTT4 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
- e678db3a19f3b0c4404c916ab81008251e5aac492194977ad7f5018875e18291
- request
- aeaf290a3c304baab3c660c1d5dad23c1d1803a19f8c2c4fbe915a48dcb5de7c
- transaction
- 989a6ab01dc946940c51c7ef2926305639e7a177604fcf0ef913d7e47b4e8994computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13224
the chainentry 13224
- sealed to the entry before
- ba086c130278953f0f405b5a95031beb7d9d8ebc2b337bc21dfed8c21dad597e
- this leaf
- e0fc0dbbe0859a28f5735e32b3630f329eda8c959c5bdab31a0ff1bb7f591996
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bteRuHT+BlabQUt4yujIM34jUplsS5R3WzTC3AAjAEO0LxgkvXHl2VTRo6ZRRvmURlYlLxYSG4lhI0MHisBTDQ==