livelog 24,007 entries · root 811c12e03c8a · read 04:02:43
the record/entry 23328
DENY
refused before it reached the network
op 0 pays GD3HDIMFZDOH5MQSWVZQOTUYUFNX67U5BENWIPFHFVEPXB2D6YBUBFFG, which is not in the allowlist
decided in 8.426ms2026-08-26 15:17:34
why2 reasons
mandatedestination_not_allowed

op 0 pays GD3HDIMFZDOH5MQSWVZQOTUYUFNX67U5BENWIPFHFVEPXB2D6YBUBFFG, which is not in the allowlist

counterpartycounterparty_denied

GD3HDIMFZDOH5MQSWVZQOTUYUFNX67U5BENWIPFHFVEPXB2D6YBUBFFG 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
a75955e7d4b3b5676c6617342a98ab3657958f254762bc1ed122591570608959
request
b5ca1dbf9a42fb0b757c6167b4cf8aac8dcbc0a7201fe17ea4f7566475498dee
transaction
ee1600c15adbcf36cdb730ef687e5fce4b6a2c5370e48eb9dae3e7f89862af1f
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23328
recomputing…
the chainentry 23328
sealed to the entry before
b5146a89e3c8da2e9a0895c1dabadf1b418767b55ab6afe80923f786c1e5f54f
this leaf
456c76c608b13fa6450097e96b83fe571c825bb13f490509c1aac79b142b3a09
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
tx4fxqeHasEIRIeOh2ehplDLWxWZU5F1EMTKbpFlYL9BSmQEg1mDzYbPwb2AIEkFEwfSc88B5vnwcS0BIrR2Cg==