livelog 16,427 entries · root 10a4d709f6e7 · read 06:28:13
the record/entry 212
DENY
refused before it reached the network
op 0 pays GCSTH3MUEGILCBBDCQMKC2ZJ4DZFTIVBCMZKGDPKDQA4CM4VKXHU25KC, which is not in the allowlist
decided in 6.465ms2026-08-08 18:46:13
why2 reasons
mandatedestination_not_allowed

op 0 pays GCSTH3MUEGILCBBDCQMKC2ZJ4DZFTIVBCMZKGDPKDQA4CM4VKXHU25KC, which is not in the allowlist

counterpartycounterparty_denied

GCSTH3MUEGILCBBDCQMKC2ZJ4DZFTIVBCMZKGDPKDQA4CM4VKXHU25KC 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
68e165cc1154e7dcc87891e25b619d32a28fc51a89108e716095b3be5dc3e56e
request
d692d26f893284b38607bb6e4e295421819bdea66f70ca95d0bd3a88b008e3d5
transaction
a21c50b81640048101c6e125ab8ced2063a7d296b5b981d5c588b8f5e4745c25
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 212
recomputing…
the chainentry 212
sealed to the entry before
6049cbb672c9a44738cc6929bf308ca944b8f5233f8679e6e3e6085a6b7098a1
this leaf
7bff797b7131e9d07e4fffa032b56cc0278dbec12aa2e178c076815dcf2b4cf2
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
ZB6+3GHXlF8QSX5dDUax8Pqv+fHY1ruLPMdHewLGFJmmEGhx5nJ/wwMM6KP9l1wtldnXpcuW9ykhElkd78UEAQ==