livelog 9,815 entries · root 397a24896094 · read 03:12:33
the record/entry 9639
DENY
refused before it reached the network
op 0 pays GBVVQIXG445ZBSQA5VAFCMWZPAFFLQTQ3RF5Q2OPBBOI3FPOWMPU5IJJ, which is not in the allowlist
decided in 7.292ms2026-08-15 23:57:24
why2 reasons
mandatedestination_not_allowed

op 0 pays GBVVQIXG445ZBSQA5VAFCMWZPAFFLQTQ3RF5Q2OPBBOI3FPOWMPU5IJJ, which is not in the allowlist

counterpartycounterparty_denied

GBVVQIXG445ZBSQA5VAFCMWZPAFFLQTQ3RF5Q2OPBBOI3FPOWMPU5IJJ 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
93d7db236c7c8d5ef6b9e0a4f722a603ec94a76fb9ad9cd13061c7a5e288b0db
request
f9dd9e9dac8e40671413b154df9c9dc16c6e21865a106fc76dff800daff2d210
transaction
e11da61056d06a96a372efea1308e2f61d8f84d95ee01ed7b19eed06dfec5790
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9639
recomputing…
the chainentry 9639
sealed to the entry before
a0c6698bc577fa5b2d85b59fbee5980933eab76f21e9386f25a31bff825befa2
this leaf
e9c81aa10e3b08a81bafd5591c5b57061ee9131683517f24cbea66666ee0cac6
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
bRXs85gQ4oEGNxLkkJ3Ge3bm5zoB+u1JEZD3avgNbdeef3dKcgO8rbbqQ/fAJHT1CBdVai1W95s5z+hwH+KeDQ==