livelog 56,425 entries · root effcc76de379 · read 19:46:28
the record/entry 55618
DENY
refused before it reached the network
op 0 pays GD3K7MSVTCB54HBUQ2NUY5VSL6XR5JEXIPFPI6UXRAOYJUJD5NFJFWT5, which is not in the allowlist
decided in 6.880ms2026-09-20 05:10:18
why2 reasons
mandatedestination_not_allowed

op 0 pays GD3K7MSVTCB54HBUQ2NUY5VSL6XR5JEXIPFPI6UXRAOYJUJD5NFJFWT5, which is not in the allowlist

counterpartycounterparty_denied

GD3K7MSVTCB54HBUQ2NUY5VSL6XR5JEXIPFPI6UXRAOYJUJD5NFJFWT5 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
c1e4c4c769dda51d3bcb08495bbe4b34f79e1c008935ae165a48ad92ae7a9189
request
abb380e3851a87b310328d2df2ffda9e1839d2e40b27ad2ba688dfc35807ab38
transaction
663ae50b3aa022ec3c0e20f2c9df5fcdf713de622f3e3a375faa675ab7a05211
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55618
recomputing…
the chainentry 55618
sealed to the entry before
6ab484686511e92cf86c892c298f804a66bb34922f6e632237e156e6b59db440
this leaf
655fa48714bd0800166a924ac17a75805b7a9787f33bee775602f365f837df31
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
XJa9EFdsiPlXjiDdpNZaQj7yh3HfsaOiVrFbCIHwdtuahjZP85Bze1R8y7aXLbe2YWVPLzf0IoBEnSa1UvQuBA==