why2 reasons
mandatedestination_not_allowed
op 0 pays GD4TTWLCESJ5Q3KY6N22DXDZSEVBZEHDNUTEXXY6ZX7ZZ5YWWLEHFO2J, which is not in the allowlist
counterpartycounterparty_denied
GD4TTWLCESJ5Q3KY6N22DXDZSEVBZEHDNUTEXXY6ZX7ZZ5YWWLEHFO2J 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
- 73aef2470ebba7a060f3d45461ebef728dc6224191d02b9ed28b183691aed6f1
- request
- 56512de6fe5cae8fcb3acc47c02c6d58e84f25139f6d291e1acd6f39605b9dc2
- transaction
- aafb94a6666fc829806bd91bf395ad63648dbcc4e85f3c24b87bea061ea419a4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38296
the chainentry 38296
- sealed to the entry before
- 27a9ef46891c3b3ab704bf5eb17a239a44d7d184efa75a5ab68c4daf3af18366
- this leaf
- a2abe6f2ccd1054308fd94c7edfb8e07ed6eaf2fa760e049be48a45f16f5fb63
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8D1/EbQTegwaoNW2eIAljKJv5hPJvnXhSy5kEKynStggLviVi9jLw6KwV2y58+x+hubvQ3ucJmhdZ6CmJKHUAg==