livelog 15,778 entries · root 54d79eb150b7 · read 18:43:29
the record/entry 1049
DENY
refused before it reached the network
op 0 pays GCM3PVF7IRQIXZD6DZN7IYX3IQUIQTQUWRWYXGBIKGDD3QVQB3HAVNGU, which is not in the allowlist
decided in 5.445ms2026-08-09 08:31:13
why2 reasons
mandatedestination_not_allowed

op 0 pays GCM3PVF7IRQIXZD6DZN7IYX3IQUIQTQUWRWYXGBIKGDD3QVQB3HAVNGU, which is not in the allowlist

counterpartycounterparty_denied

GCM3PVF7IRQIXZD6DZN7IYX3IQUIQTQUWRWYXGBIKGDD3QVQB3HAVNGU 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
e025da6eb716671c6191b72cfde109ab3d967f62902af4975e636a1a18516e36
request
d1d0b1d099280380c7e12f705bed17b3c6b459a9e9cefc3747e53078c242e59f
transaction
756beaec23a953c0307c8bd9ede3c61972aa0a966bcf3f2f6726cd255c04b1c8
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1049
recomputing…
the chainentry 1049
sealed to the entry before
daae8aee49bbed81cacaae46bf70fd7e5fab326d29bffb0fc82aeb8b874e745a
this leaf
617976ff56c0aed63b1dc96d52816ec23e6fccee938f69d46ec3547c16d4bb86
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
0Gzns/ZVNraG3OsQS+a83s+hRlOhdK4iCStDO516j2B3MqairgLTLEt+BbrCzU1EYyDkBOrIyNUHl6th0Hn8CQ==