livelog 26,187 entries · root 380e78ad143c · read 20:27:53
the record/entry 25824
DENY
refused before it reached the network
op 0 pays GBZDHSTLZY7VDXRVPQGUWVP4BWIZV6RIPWQMJEPL4H4PMOUNZFEA22NW, which is not in the allowlist
decided in 8.085ms2026-08-28 13:42:32
why2 reasons
mandatedestination_not_allowed

op 0 pays GBZDHSTLZY7VDXRVPQGUWVP4BWIZV6RIPWQMJEPL4H4PMOUNZFEA22NW, which is not in the allowlist

counterpartycounterparty_denied

GBZDHSTLZY7VDXRVPQGUWVP4BWIZV6RIPWQMJEPL4H4PMOUNZFEA22NW 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
75e7274c8ab386058cb3c40401223edfa0eb70cc56b459f67af4fb2d7513dd3f
request
f0232dce2a0a53e4e9a44f2bcf036041b5230b29973a2b68546a0e4d4fb70ad4
transaction
778463f75f768e131a5a1e1f8877e3704c17a1c170ced730ec9be91c6b5b4ebe
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25824
recomputing…
the chainentry 25824
sealed to the entry before
80c6a411af1b48f1dde1991b94cc80f26000e0cc403a5f34cb039ec446d80843
this leaf
c1f85ba645eac8e02b40251f1e2baf3bd77bdfacf3546ae044eefe9a2b4cea0b
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
Y4HkV3Xi2D148i65zpGViyoEtHeMijF1n71AAg4d4oGRkz1NnMiInjvdBL2c3FgjZnLd+pCGUBXaTKvhqiHFCw==