why2 reasons
mandatedestination_not_allowed
op 0 pays GDDYCWR6VG74EZOXKJ5JVZI6T4ZCB6N6YYLOBKCROLLTIWAPJYT6ZS2Y, which is not in the allowlist
counterpartycounterparty_denied
GDDYCWR6VG74EZOXKJ5JVZI6T4ZCB6N6YYLOBKCROLLTIWAPJYT6ZS2Y 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
- 9f03d53002afdca525cf1c8be560ee9a40dbced153f339d1afd73add4c758aa3
- request
- dee27575147b04e0c352e88b5bc8f596cded7a46f3d53186da71cd4f88762e11
- transaction
- 9fe53377d4fa6c50c1b02a8aa6ceb0ef9a9bc39cc88d147b69e379ec7dd450b8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1601
the chainentry 1601
- sealed to the entry before
- 5434b887fb74bb485ea2c32c74af29b6fb9dddf3e998b81681114417e27c2e1b
- this leaf
- 294a528cc45af0411406c2cd71411eedde0961ca868d776a1a15654a4ef40b8e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hWeSJUmrW3kbYsHa7nN/EtSG4v1y6QUzUMaRJSHjnjrQTDuNM0KnpKtE8+sxEPY7GyBi7+EYomIHUQPtA6KUBA==