livelog 12,678 entries · root 059261009ba7 · read 08:02:50
the record/entry 5039
DENY
refused before it reached the network
op 0 pays GD54QEGTFGEST6ZVLCLZCZMUX3JFFYWRVS63ZIQVHGRAT4EUHMEYG5WT, which is not in the allowlist
decided in 6.008ms2026-08-12 08:42:29
why2 reasons
mandatedestination_not_allowed

op 0 pays GD54QEGTFGEST6ZVLCLZCZMUX3JFFYWRVS63ZIQVHGRAT4EUHMEYG5WT, which is not in the allowlist

counterpartycounterparty_denied

GD54QEGTFGEST6ZVLCLZCZMUX3JFFYWRVS63ZIQVHGRAT4EUHMEYG5WT 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
2091c7b69864c650f1bedf2563ff2d1904ed82c6e2f639eb1e17e76fcaba98e4
request
69ab580858d7992d3acb781ad32f5ab8cc2c5026c24c528075fab4d4e141ad03
transaction
4f38a65f36b2ed413d377fb373904c449bd8de48e740cca0afa197cfed8fba54
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5039
recomputing…
the chainentry 5039
sealed to the entry before
b2321321c7286c235ae157e00a0305871b746f586ff94933361345005ba7d915
this leaf
596ef384a4688e13074f6366c5fff4921a8ac9ee0733ac539324ee2b12448593
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
omA0drkW2MiBw1BOegYBNHR5Xdon0drUbKISV5qSpTm7Z8+V6JfpvbQ1Y1Ui1GlqD2z04CmayZdFBvzsQoXEDg==