livelog 31,093 entries · root 5994b0e3f3b6 · read 14:52:50
the record/entry 30024
DENY
refused before it reached the network
op 0 pays GBMZP6JWYJ6ZIM2VW6XEY2I2E76ZLTSAGU4AWZMXJ764BZHZF3U6TICI, which is not in the allowlist
decided in 8.202ms2026-08-31 18:47:38
why2 reasons
mandatedestination_not_allowed

op 0 pays GBMZP6JWYJ6ZIM2VW6XEY2I2E76ZLTSAGU4AWZMXJ764BZHZF3U6TICI, which is not in the allowlist

counterpartycounterparty_denied

GBMZP6JWYJ6ZIM2VW6XEY2I2E76ZLTSAGU4AWZMXJ764BZHZF3U6TICI 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
daffbb3a008cf751b8ce7a237a43484c50a713acd944927fbbb7a4db1e133ab4
request
ec211b3e1bf0d783d5442b8088c3acced18489053e487c6d60e203a451963947
transaction
71bdb005e38d870ecf5b9494301356b515221dd8d5b52eddc18ab6c0e40202f4
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30024
recomputing…
the chainentry 30024
sealed to the entry before
c77642cb1a9dafea5d18577d57eacc09810cf9d2ad80c51a08c402150163e80e
this leaf
c737d04df1a275bde8081d07c80c97b3aed6a53084e2297af421ae8ede879712
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
kQQdf+nIEGoEOTKZa4zYS1DqNTVYNj4pnJFJTMn3DNadD+ji29nnvM/rV7BRlIN+6UT59YKiTUShvpGAd6oDBQ==