livelog 33,821 entries · root 130394471b14 · read 17:02:48
the record/entry 33700
DENY
refused before it reached the network
op 0 pays GDCP6UCITGPVWU64NKBVOQG5MSMDFJAR4ZHLXHILSHQ35PZA76ZGCAGO, which is not in the allowlist
decided in 7.437ms2026-09-03 14:47:34
why2 reasons
mandatedestination_not_allowed

op 0 pays GDCP6UCITGPVWU64NKBVOQG5MSMDFJAR4ZHLXHILSHQ35PZA76ZGCAGO, which is not in the allowlist

counterpartycounterparty_denied

GDCP6UCITGPVWU64NKBVOQG5MSMDFJAR4ZHLXHILSHQ35PZA76ZGCAGO 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
30afa75cab168a52214b81427555212f3b6061149aae71bb28d09c8003e1b5a2
request
a3c0ffec31fbcc729d217fbcd384e297e3afc4cc3cce5f0072f63755192778ac
transaction
ab3850ffb3d57f419a41c140551a0d3e8e53d3c053941634e16d4d37102a4877
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33700
recomputing…
the chainentry 33700
sealed to the entry before
8f56f590c86ed8a59893bf5b30b30a53537fcfaae7d55c18ff2c82ff93d54c16
this leaf
7eaf63d3b7fbc0213f5f8779db8b1162efbcfc2f453277291208feb18061da3b
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
nkOgg0MfsfgkGEz4VNftmd2MB41VeauBqvCpD4zGVwUNnN3K+atlaiBYbY0ukYM8l52LUb0ZeNg3s71YP92SDw==