why2 reasons
mandatedestination_not_allowed
op 0 pays GDZA6FXARSLWUEMETJKUXN2YW4EUNFKAPQRA4Y6S3OAIIZSYQIMQKAHU, which is not in the allowlist
counterpartycounterparty_denied
GDZA6FXARSLWUEMETJKUXN2YW4EUNFKAPQRA4Y6S3OAIIZSYQIMQKAHU is on the screening list: force-escalated by the watchdog: the pattern "address-poisoning" was refused 4 times in this session, first at 2026-09-16T08:27:33.696Z
what it was decided fromfingerprints
- rule compiled from it
- 3650bc71430b665d1d2b34b5ca8d14e4c7e67ef71938f54ab6557f3035e6d115
- request
- c757af2a4c10669b65a225b78261ee7a6dad0b8be3dc0b3e546b7e3252226ae7
- transaction
- 4494f13ec05fc23dd8a8d625fce14ee4198b1d24754c40a5c02964c32e8ba915computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50700
the chainentry 50700
- sealed to the entry before
- 2043ada05054119b029b8fdb0702491bc9128aca48cc843ef0397c67f39b2a63
- this leaf
- ca791963e419b94429d48f1764cabf96304a3b57581834830aecfdac59b8402d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9wNqDrzmUDTRvfPInuiopwMqygb1jzyON+6EMD98B+t2a5p2qoqW8THwJtGvQ8W/k/IQLYpX/ghY6Q46lWbkBQ==