livelog 36,460 entries · root e0ea829c21fe · read 18:42:51
the record/entry 36326
DENY
refused before it reached the network
op 0 pays GDMLMRXADKH6SUXJOUMJK6PGLD4TPO53PVI6E7WSLOIHY3EWDZKDE24M, which is not in the allowlist
decided in 7.174ms2026-09-05 16:22:38
why2 reasons
mandatedestination_not_allowed

op 0 pays GDMLMRXADKH6SUXJOUMJK6PGLD4TPO53PVI6E7WSLOIHY3EWDZKDE24M, which is not in the allowlist

counterpartycounterparty_denied

GDMLMRXADKH6SUXJOUMJK6PGLD4TPO53PVI6E7WSLOIHY3EWDZKDE24M 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
b056cacfc006d62286965c3de082dc4e7a111dae16977ccc9713db0beb557198
request
658a982eb62245d027c02f3225394340b0c26e6ecb85573cdd10d6c1f45f65c3
transaction
68ce8498429c9b6f2c0de2009aeecb535dd6dcacfd30c127c338d3884323ab01
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36326
recomputing…
the chainentry 36326
sealed to the entry before
d2624294adf67d36df2e51b7d55b50906ea2692b6ad8ce882f89c07a5b1238a5
this leaf
1ad48a4c7e64ee51b9880d49ed082108c522d532fe15c8cb0d0a65bbe7896722
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
snoKjd9h3pAKFgwSqp5//t0aOJVcIHunZfMNkeoOXfvw34iCRlsBixf7YXxFRYXXpD9+PllS1wc+QEenRmwXDA==