why2 reasons
mandatedestination_not_allowed
op 0 pays GD5EJDVZB6Q33UCUR4FPI5XCE2TT6YO4U7QFFLZW5H4OA235JHQSYNWF, which is not in the allowlist
counterpartycounterparty_denied
GD5EJDVZB6Q33UCUR4FPI5XCE2TT6YO4U7QFFLZW5H4OA235JHQSYNWF 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
- a57548d981fb922c50d6d608749162c42b0266f291e321f3138a184cfd836fca
- request
- 5fe4bbf18df5f2e222c5ba89468ef2c4d4499a68f37bc67c74d5dd1ca3c3dee9
- transaction
- 7d97cb2daa14d5fe0db56e434f036ae19bcef743d37b2f5a526f8de860c5a002computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30908
the chainentry 30908
- sealed to the entry before
- 9f573d0b02dfba2ddc42aa58f4e4a39b00024a58345230e969664a457477294d
- this leaf
- aa9a963534a7df0e1f72c4593577f9437efe8923a17628618bf1f0d924e7eadb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DmCOjgBM4pQZCYHzCoNz4SxFFu+EWJ/d+TkCw9pvF5xhdMYWJbX9stLaBIlBYWWPpUzqZt2zNSRq9xki00UXBw==