livelog 15,868 entries · root 6e74d57102b1 · read 20:17:48
the record/entry 923
DENY
refused before it reached the network
op 0 pays GCPABBJAGUIB655ASEBWFRMOZC42LLPFTYD7W3AYGTGCYHKKCFBMRSK7, which is not in the allowlist
decided in 6.783ms2026-08-09 06:40:03
why2 reasons
mandatedestination_not_allowed

op 0 pays GCPABBJAGUIB655ASEBWFRMOZC42LLPFTYD7W3AYGTGCYHKKCFBMRSK7, which is not in the allowlist

counterpartycounterparty_denied

GCPABBJAGUIB655ASEBWFRMOZC42LLPFTYD7W3AYGTGCYHKKCFBMRSK7 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
acf9f86dc3010067aac6f3ceccf7c406384bfeb4e3ae75a8be878fb6b7ad9e6f
request
39b273a070ede52944b6a129714a763193256d0c70168fe91aeb5fae890d889f
transaction
4899a4c26e73315eb2369516dc40afdd73bd8a0663c277a65aafb9fda91ed46c
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 923
recomputing…
the chainentry 923
sealed to the entry before
90d7f44d7a485f4469704af08e84d9acca946dbf2ac44cfce8a829f61d8b7e18
this leaf
56c2e945743f3e5de4ed55a42a0762aae198277ac17003ff6bcbcad9ec49730b
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
tCYHxgKA8Y9O1UPbNSeahSsQIw7TCLhA1fxM+ruLw8umFpD5DGn1Xepht4F11Rm7vhJJy7g1SMN07+74ewHWDA==