livelog 16,342 entries · root 3226e406ab17 · read 04:53:31
the record/entry 312
DENY
refused before it reached the network
op 0 pays GCXRN3KYAXKTLCD5JFUVOLV3YYYWABLT3ADV2XYGOHER6FTFCM2CYH2M, which is not in the allowlist
decided in 5.346ms2026-08-08 20:26:12
why2 reasons
mandatedestination_not_allowed

op 0 pays GCXRN3KYAXKTLCD5JFUVOLV3YYYWABLT3ADV2XYGOHER6FTFCM2CYH2M, which is not in the allowlist

counterpartycounterparty_denied

GCXRN3KYAXKTLCD5JFUVOLV3YYYWABLT3ADV2XYGOHER6FTFCM2CYH2M 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
c7973429695ddab86127a432843a3947dbca790f594f6bd7dc532eff241c028d
request
bd1a8eb9332ed83b71939e5e51f5bf3d2ea467ad1272988c2b5ef75616181f0c
transaction
a5daee0e472384cdea23af070fbd4832dd6f9c09aab97eb69b6a6910f44a0e17
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 312
recomputing…
the chainentry 312
sealed to the entry before
a180301d724b0f8f2a87cf02937eea20b8b3d30c38aeb832b7e6cfeabd2d436f
this leaf
c1d0eb6fdd529411e0a1f9e8abed2cdf5a0041b0373c8367f2c402f67386ba92
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
PGCZfQPQ3lXUmxUQUG6l4bXMA7Fw2XxofQBI++ajX+czjEo+VTLC5Mx4XuVsV8gCI7537oCbiPvBRBNMNfeYDg==