livelog 15,951 entries · root dd7a75e800e4 · read 21:42:55
the record/entry 787
DENY
refused before it reached the network
op 0 pays GDNZN6UJFRL2LV4WHNLYMQCER72PK52T4ITJ3PE2W46W5CR3U7SSPNAK, which is not in the allowlist
decided in 6.568ms2026-08-09 04:26:16
why2 reasons
mandatedestination_not_allowed

op 0 pays GDNZN6UJFRL2LV4WHNLYMQCER72PK52T4ITJ3PE2W46W5CR3U7SSPNAK, which is not in the allowlist

counterpartycounterparty_denied

GDNZN6UJFRL2LV4WHNLYMQCER72PK52T4ITJ3PE2W46W5CR3U7SSPNAK 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
a09934723f92dc2d23bacb70575f865801502627c6e40d52d5c0085b646336d5
request
1bb9e0c7861e3e760c67746305d63604d094dc0e5f0ad5c390eae648b33cd878
transaction
831f9dc09c15871876e177760864c1f0076bad1694c4beda212f2d9fa231a523
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 787
recomputing…
the chainentry 787
sealed to the entry before
8a39f9f5d40a24107de7ec8186cff83e67b9dae27c19e2550e2ab648dc2e8186
this leaf
15f3531b34542ae1926b70f727d316df308a9fae7948e7f4dba0fa2f73cd1012
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
qD7ZYq1wgt2SiFeBQ84qhmM6rRJMRGFKK5Qv95+o1X8rVYKeE620yYydSvUDMNWDa9fAp0LnBh/U7B98SObaDg==