livelog 16,273 entries · root d3e7ddaa69e5 · read 03:32:42
the record/entry 392
DENY
refused before it reached the network
op 0 pays GDPTCLD6EBZBLRJ46UIE7CKRDVXSYF4Z56B2FETFYIBXPGGTR5YAYBSD, which is not in the allowlist
decided in 7.135ms2026-08-08 21:46:14
why2 reasons
mandatedestination_not_allowed

op 0 pays GDPTCLD6EBZBLRJ46UIE7CKRDVXSYF4Z56B2FETFYIBXPGGTR5YAYBSD, which is not in the allowlist

counterpartycounterparty_denied

GDPTCLD6EBZBLRJ46UIE7CKRDVXSYF4Z56B2FETFYIBXPGGTR5YAYBSD 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
af0d7f0243af830789e9b1da1b70a84adf510c7bec2effde248beb43b90a9aaf
request
9f7dee654a364525717fad0de28b9ff8257c58a878ff22a6628b615bfd72b7a6
transaction
a610de7e31237e02954502e9dac3ca74d7f37d0e2d218780e18062b4f0747e2e
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 392
recomputing…
the chainentry 392
sealed to the entry before
cde608ab900de293ea2ad4e9e4149bec23ab3c7b568b77e2f788d11e65b6e47b
this leaf
edc8ebe827ea0b6be572e2098612b53484ca89f6ebbd848e8350ed715f8bd9df
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
kqy5usrJGlktHyzvSL4EbVbnnf1h8yxeSSZQSFnOTrbOBMEIG4/7Ee65bcw5XDo8YX+JtnN1dGv8Tcn++TD6DQ==