livelog 33,229 entries · root 370eecb0a8dc · read 06:02:58
the record/entry 33089
DENY
refused before it reached the network
op 0 pays GDHHXVJCXDBLGRP5YKPPRKEJN47GX3NC4WJDBM3M4FYUC4U6M4HZEAXD, which is not in the allowlist
decided in 6.985ms2026-09-03 03:22:38
why2 reasons
mandatedestination_not_allowed

op 0 pays GDHHXVJCXDBLGRP5YKPPRKEJN47GX3NC4WJDBM3M4FYUC4U6M4HZEAXD, which is not in the allowlist

counterpartycounterparty_denied

GDHHXVJCXDBLGRP5YKPPRKEJN47GX3NC4WJDBM3M4FYUC4U6M4HZEAXD 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
8a1c94375ccfc1b7ab7a1129f17681744cd9409de917d4db63214ce7655da3cd
request
4fbe9e3ba01e957c9782db869a7172d2b782556f93a4ef63b1cc4514dcbec9c4
transaction
e375bbe73a746cd0874e96b0cfc6bb8e91a7aabdecbfa6f77b54b1b5834cbca1
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33089
recomputing…
the chainentry 33089
sealed to the entry before
fc955aebce91080687a5764d4567567f8994f490f2301f2ed16ac13cb03df6b7
this leaf
202e42ece75bae1f7cc6e7950f98266fdf9f99312b3f60c09611de0a1acc6bc5
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
xjiNM+lJrhEKiQ5QtWGLLeRRvX6mW98yLw2DqnL6euPcoQAt3a9NH56Gh4rQUxZV7Y5gyGf7p9GBp/BU9KHhDg==