livelog 16,432 entries · root e55cd66e0c4d · read 06:32:31
the record/entry 242
DENY
refused before it reached the network
op 0 pays GDMPFI57YEBA5V45F3FPWJ2M2GRXG4YQW7DVDH5RWNCUSCBE76567YLU, which is not in the allowlist
decided in 5.789ms2026-08-08 19:16:15
why2 reasons
mandatedestination_not_allowed

op 0 pays GDMPFI57YEBA5V45F3FPWJ2M2GRXG4YQW7DVDH5RWNCUSCBE76567YLU, which is not in the allowlist

counterpartycounterparty_denied

GDMPFI57YEBA5V45F3FPWJ2M2GRXG4YQW7DVDH5RWNCUSCBE76567YLU 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
346786ddf2ae9d91fd3b4cb1a9293d764145db16a6a1ecfe5b7b6518976e823e
request
6818a9869a035d030c00871a8d5e950677b4b26c3c3bc541b6ed228e7d8af79c
transaction
fa52d3809e70d5c616054f08111d82ed197b9c7aa26cf47dc9897d4f6844cb79
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 242
recomputing…
the chainentry 242
sealed to the entry before
1c240b9e8552860a8733d4bf27abf5a2e601f21b3dd5a5ea5894f5fe5ffc1d72
this leaf
b8bda2e0a54082981d649f01503f60932eb41080d945a8579d6945cdc4694f75
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
rkM9DCWYe8XEkVA4NTPQtQbj+BRqMXD908RBLNP45PQCw5eCu/NCltFKYpLEHko0snYFrhtLyjuEZQy2jWSzDw==