livelog 22,256 entries · root b39f513e7600 · read 19:32:32
the record/entry 20934
DENY
refused before it reached the network
op 0 pays GDNS53PEGRUVGRT4Y2TZGZMWGX447SFRTUTGYBTDBOPZ5IWX6B7TD7EC, which is not in the allowlist
decided in 6.599ms2026-08-24 18:32:31
why2 reasons
mandatedestination_not_allowed

op 0 pays GDNS53PEGRUVGRT4Y2TZGZMWGX447SFRTUTGYBTDBOPZ5IWX6B7TD7EC, which is not in the allowlist

counterpartycounterparty_denied

GDNS53PEGRUVGRT4Y2TZGZMWGX447SFRTUTGYBTDBOPZ5IWX6B7TD7EC 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
37fcc08f133a63cb80dac5151bcb5e508df2f385342403b9c0a7fae327a09fd8
request
8031db0727db90c6eeb9d97edfd3ded2c2f4e1d5408461f65f04808b4f04131b
transaction
6b8dbd2a3c063b49810d9af0fd7df70edeeb3e655bca3548df36f5324381e2bd
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20934
recomputing…
the chainentry 20934
sealed to the entry before
35768ccb00e6b7d21d53628033ec0eb615f26b0c2d3cd5d30a489de0fa38a900
this leaf
1d205449352386f32127fd830ca57f6ca31f6c1abc9ff239ff29dae71ad3f6ff
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
u5tvXJUIrTzHezmVDX8KIP9n3T1lYSVqzGREgtLDvXbVY79N4PnEkPDoobMFuP4qR1Ou4aqbFmC199xa4b8dBA==