livelog 11,330 entries · root 4775a5f3cb0e · read 07:22:55
the record/entry 6959
DENY
refused before it reached the network
op 0 pays GAEVOONTIVE2LATODRBHCDSDKLPDFYILTGMLFBZ66TPFTIZADFQ6XRMU, which is not in the allowlist
decided in 5.419ms2026-08-13 21:37:30
why2 reasons
mandatedestination_not_allowed

op 0 pays GAEVOONTIVE2LATODRBHCDSDKLPDFYILTGMLFBZ66TPFTIZADFQ6XRMU, which is not in the allowlist

counterpartycounterparty_denied

GAEVOONTIVE2LATODRBHCDSDKLPDFYILTGMLFBZ66TPFTIZADFQ6XRMU 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
2547a8214175d7ae0c8373b277252fe4281262f8b62ab14438c618409adbf659
request
3561f91452b304b4352e31e23246c7788df38db5c2e0c5e95ef7eca29cf49c6f
transaction
5638e0e2e6f4164ad7c10be8f1d32a87166658be8dc8067d72c0ae003ba7e2ea
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6959
recomputing…
the chainentry 6959
sealed to the entry before
314ff282215b5fcb2e14b82e11c9ab328aae3761e1c64b489033ed4d82721863
this leaf
c356d4377e454176631ce62589ca489d5a4a2b3d75193e94d290d52985fd1a5c
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
p7mtbZv0qjHqKD64GWomZRPWr4IQr5lubQ2IcGy7cfebWqEtxBkeNuacXof1hJeXf3ETREVfwQNyYBjEFfR+Bw==