livelog 12,423 entries · root 226714711544 · read 03:23:14
the record/entry 5302
DENY
refused before it reached the network
op 0 pays GB3IASYPTFUOWCBDIUXBBM2IDTEBAHZ7XR6WOGDFSLJYDNZGHSWJAEPG, which is not in the allowlist
decided in 5.865ms2026-08-12 13:47:29
why2 reasons
mandatedestination_not_allowed

op 0 pays GB3IASYPTFUOWCBDIUXBBM2IDTEBAHZ7XR6WOGDFSLJYDNZGHSWJAEPG, which is not in the allowlist

counterpartycounterparty_denied

GB3IASYPTFUOWCBDIUXBBM2IDTEBAHZ7XR6WOGDFSLJYDNZGHSWJAEPG 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
9f828ab010107ad61155a1e13a49a5a21ddba778a93d9b15bd62d25c02ac5247
request
2aeb05b0dbd7e5eccfc0561d1529d4c2b211f43b464f822949c2817a93f48ad4
transaction
05eadba6518b2e840f456975fd8bc429c8ba5479890b48f3c53e32fc78644d1a
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5302
recomputing…
the chainentry 5302
sealed to the entry before
a423ff6c94b64414091684c1ab88d6b0ef136d50c114d12514265c980d6f944c
this leaf
6d9f970fc149f0b7e6313283d34bff0565166d8abd6bfb40d46927c51d53dec8
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
I8CodfAYTi4YYwUm+GVaK3AQVXO6MWBYqJEQSbazQu7wHUiL2gAIen5NugLVZWHxbggBhqwE+t6B0zJj5hMcCg==