livelog 34,166 entries · root dc7f854a3e52 · read 23:13:03
the record/entry 33989
DENY
refused before it reached the network
op 0 pays GDKPZHAX3HBHJM3D6ONBGHEEKS25A74MINPJNLLCRP65KTUDK6TTV6FJ, which is not in the allowlist
decided in 7.563ms2026-09-03 20:12:35
why2 reasons
mandatedestination_not_allowed

op 0 pays GDKPZHAX3HBHJM3D6ONBGHEEKS25A74MINPJNLLCRP65KTUDK6TTV6FJ, which is not in the allowlist

counterpartycounterparty_denied

GDKPZHAX3HBHJM3D6ONBGHEEKS25A74MINPJNLLCRP65KTUDK6TTV6FJ 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
6544841331f05d768bfd80011feb0ffc4ae27d5b73ef037ff854ec9b5f0f0f3c
request
a92e8fbf81ed6bc51590e3fc62147038746097d710de73f59eca98c66dc199c0
transaction
f72ebfb3961b332a45c8980f7648448084e44ead5767278e293c793e3be4d535
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33989
recomputing…
the chainentry 33989
sealed to the entry before
447579345bda80899ab0366b631cf1c34c49a010092edf7b539022350bbe41cd
this leaf
27b7a37e8f7d82de797ad8822585000d6b13ddb6f18f84c371e57c67218907ce
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
is1pENYmcjuwuMus98jfc6+66sdZ9UsRqvnzd8x2QA/hmm55BhjXhLzHg4ABIeEwk+69zwC0DEpHxj4pTg/JAw==