why2 reasons
mandatedestination_not_allowed
op 0 pays GDDPN6QF3Z6COXZFVBIEVGT4JZESOVMZTUZ3PZTOSFNIL3FFW7DNBBFW, which is not in the allowlist
counterpartycounterparty_denied
GDDPN6QF3Z6COXZFVBIEVGT4JZESOVMZTUZ3PZTOSFNIL3FFW7DNBBFW 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
- 6aafd9cf7c8de91fc53d1945e40f96a944514dd304254ac438384bf89147cd75
- request
- 28ce0168a30f5c2d492495a5f94aa7d9ce10b73dc77460595bebbafb90331ada
- transaction
- 73f63f873424392fe5a99fa280995724b662d123e7c26219b97eaaaf0f9479f2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7260
the chainentry 7260
- sealed to the entry before
- 49e17438e3e8efa5ffe1166ecc1d87a748d30b6fb670d7366bb8e387b0665332
- this leaf
- 88ef55f4d4cbb2a3c5423ec45e678a720469c5b20136eb5a3b3102e037f1e859
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IKZ3vIBQKZTlK7A8rmAid+0mVu/G4bwgGHBVZNtF4AYE8nUKXQl0JzsIo68lOf9okQUI9L29CPEIOlWjJhkxDA==