livelog 27,375 entries · root 43a4de8c2277 · read 18:32:52
the record/entry 27248
DENY
refused before it reached the network
op 0 pays GD3BJ4KAUHRYCBKN5AREZHRZ54EAFTC62655QFLIMCM3BRJFUGSWMKNX, which is not in the allowlist
decided in 6.279ms2026-08-29 16:17:38
why2 reasons
mandatedestination_not_allowed

op 0 pays GD3BJ4KAUHRYCBKN5AREZHRZ54EAFTC62655QFLIMCM3BRJFUGSWMKNX, which is not in the allowlist

counterpartycounterparty_denied

GD3BJ4KAUHRYCBKN5AREZHRZ54EAFTC62655QFLIMCM3BRJFUGSWMKNX 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
a535ba997600e449e25cda6b685a521442d52744e0f8bc2e872bee46c78f134a
request
8dcb51a23a896888241aa7b5a743f4ceca631d3dc87723bd8c82c17062330baa
transaction
704384a1d0b34bdaf80df34092f69f732a8dd6eb58d0b363c1713cc7b6f9e0fa
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27248
recomputing…
the chainentry 27248
sealed to the entry before
d4a675944cad784e0b69daede33af7f132c6b14f3c0a121c8b24e29d166b0e2e
this leaf
d576b514e211d48861547666ae1b9ea6f7b98112b7fafb59c32bce08c3502d9e
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
KjWNjx7RzOuzmvjvRfDhGyfygRvDyQFMRz2ZwgNrOP4k6kgjCr6j9sANHg5LT1hwVsTppXd5yxnTmyavYdReAQ==