why2 reasons
mandatedestination_not_allowed
op 0 pays GDURS4W6W5S5GVQYEQU5T36YMWED2BNA6OPPWKM7UAQYG3ITXTKYRAMJ, which is not in the allowlist
counterpartycounterparty_denied
GDURS4W6W5S5GVQYEQU5T36YMWED2BNA6OPPWKM7UAQYG3ITXTKYRAMJ is on the screening list: force-escalated by the watchdog: the pattern "address-poisoning" was refused 2 times in this session, first at 2026-09-16T08:27:33.696Z
what it was decided fromfingerprints
- rule compiled from it
- ddde94c8abd01ef74254c230bf4cda3235ce94a75f5ffcd3fc74b0abf6db610b
- request
- 8629ee9898c043532178535284d582db19b051568b4176a87178053cbc21a92a
- transaction
- 29748e23f6ac6382cb71fcff5d2d95d80a2ac2a2733a2f55b5e3bcfad161b1ebcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50393
the chainentry 50393
- sealed to the entry before
- 0fe67c3a15eefb5c5b647a433ddb1950c36bfdce055d9b6fad73b720786a06b3
- this leaf
- c753bfb99419b360836baa30a86fb6b285da4a392dd9309f9c78c9aa5de5a17d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ktMC0ThE6+V73vaYcMUzk5fiGgV6Qv6DGpDROFc2R4RlYn87Sv16lAdaR3+SBEFcW6tih+9tvtJESJBFxvf3Cw==