livelog 16,116 entries · root 84b726c375cc · read 00:43:01
the record/entry 667
DENY
refused before it reached the network
op 0 pays GDN7KH6ZNWXFPNBDUPC6ULJYYMRYG2I6WO2AH5T2OHVFF5LWCD4LQYZD, which is not in the allowlist
decided in 6.577ms2026-08-09 02:26:15
why2 reasons
mandatedestination_not_allowed

op 0 pays GDN7KH6ZNWXFPNBDUPC6ULJYYMRYG2I6WO2AH5T2OHVFF5LWCD4LQYZD, which is not in the allowlist

counterpartycounterparty_denied

GDN7KH6ZNWXFPNBDUPC6ULJYYMRYG2I6WO2AH5T2OHVFF5LWCD4LQYZD 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
1ac765928da62085276a94966463b93be673b61531eccc8d88709ff2ccdfbb04
request
8609f28d5b148ddc5a64814ec82aed552c32087b755dde55b5831436a4ffa417
transaction
6b8289b269b8ee5bf69f41e6b7aac289e6f119bab0c5f4b2aaf4fcecb0269113
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 667
recomputing…
the chainentry 667
sealed to the entry before
a4e0798aa68619ad38d949e85b2d785e503c990a8d2f36caa554774511499c1e
this leaf
40c610d2f01245c1158423ca35b49cd1e36ef400f169b7666f0462e9d0d7562c
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
ElQ78BM7TrU+b3+Ha+8E+pY/UCd89pKnk0GxQa92v6zKzS00dCxzkTDvQvAQZlvpoTgytfdfaEFnzeZUCHbbBQ==