livelog 35,175 entries · root de2bdde3c7e4 · read 17:52:54
the record/entry 35006
DENY
refused before it reached the network
op 0 pays GC2BRHJYIBNPTAGCEPCVP2VSWQWB3PZ5HLZNEIRKL3J43ZP3DUXOP3IX, which is not in the allowlist
decided in 7.030ms2026-09-04 14:52:37
why2 reasons
mandatedestination_not_allowed

op 0 pays GC2BRHJYIBNPTAGCEPCVP2VSWQWB3PZ5HLZNEIRKL3J43ZP3DUXOP3IX, which is not in the allowlist

counterpartycounterparty_denied

GC2BRHJYIBNPTAGCEPCVP2VSWQWB3PZ5HLZNEIRKL3J43ZP3DUXOP3IX 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
bc99a913bf39cd31e1236e9effbc11e96bac7ec21d674f989b571765067bf74d
request
74e76111fbbfb5a34fe73e9b9a48b06cce45947fe7c6bce06f83f5df4cc235d6
transaction
24609c3b5a01da220410cf7b771bec846d8cf4cf4b5162c5d165f86a196459d4
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35006
recomputing…
the chainentry 35006
sealed to the entry before
b5644e96c2c20854f8e878c844323b38f88e02d8e082ac60ba9d6021f61c0dfd
this leaf
d8607e1b7901ff50f48f6f12cfd3136e7e9f1e7e91d2e7a959eb4dac08b10e81
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
PibQxhsAymNHc5Sm452XOjhS8tclFHBUx6PyiF3qG34r+Ci0w565E3jfReJgGZjClSAjhl2TexylaW1kPgC1Cg==