livelog 16,111 entries · root d34b1a75670e · read 00:38:13
the record/entry 612
DENY
refused before it reached the network
op 0 pays GDINEQ7QTMMNS24TZVNRES7VS2IHCNXSGTPM25MD5PDAZRBNJQRVTNCP, which is not in the allowlist
decided in 6.570ms2026-08-09 01:31:15
why2 reasons
mandatedestination_not_allowed

op 0 pays GDINEQ7QTMMNS24TZVNRES7VS2IHCNXSGTPM25MD5PDAZRBNJQRVTNCP, which is not in the allowlist

counterpartycounterparty_denied

GDINEQ7QTMMNS24TZVNRES7VS2IHCNXSGTPM25MD5PDAZRBNJQRVTNCP 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
78b6d821cadf851398375fbbf0e4c811af5c326002162d597a13c70da0d37930
request
e1b7e74b3ba49450c7fc34119d139bb5cafe5655eab45761551710b68f64d76a
transaction
8c0b05382fdbf91c0e8ac267334a2eed4031abe002cbf3b6156d02842074a298
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 612
recomputing…
the chainentry 612
sealed to the entry before
1beca4f14b6f9d51a15cf509532c1a051556375b6c1aa1ac3c0579f05193841b
this leaf
5d38e68cf73f36607a31325ec7e8565911e48b8ba2bdedfc788da30cf0c3fa84
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
FRhW/jaj/rWNZymwoOpCnX9me72ghy+vRaKkt7MrE8nFtzJh1LHkIqRAfqhmqIqXeuPvRSJWQm/Ix1XUsVx0AQ==