livelog 55,147 entries · root 7fa08d52415d · read 20:20:48
the record/entry 53196
DENY
refused before it reached the network
op 0 pays GB3X7ZONZSJ53E4MAK4PVOAFDDIVMHOR4LWXV2H6QTO7GFAZTTKBFFTU, which is not in the allowlist
decided in 7.290ms2026-09-18 08:45:15
why2 reasons
mandatedestination_not_allowed

op 0 pays GB3X7ZONZSJ53E4MAK4PVOAFDDIVMHOR4LWXV2H6QTO7GFAZTTKBFFTU, which is not in the allowlist

counterpartycounterparty_denied

GB3X7ZONZSJ53E4MAK4PVOAFDDIVMHOR4LWXV2H6QTO7GFAZTTKBFFTU 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
24eb745b74a470d7f8e30c9138ecfd7bb318867930965c1c0c1fc62a3f3992b4
request
9b993a5cdb3cb5b9dd5b3fec38c79791e87058c199ee7b5de3aafa530eb3e140
transaction
2f899b79aabba75f2ef74c67e8e5eb246c3fc23190229f0ba22d4e351de9fc9f
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53196
recomputing…
the chainentry 53196
sealed to the entry before
8e847d51f42f48e4850407e97c9d212ef56c3f8b282bafe41c4f7cfdf9d96798
this leaf
9e6266d50b966ca8c359555dfd7077c1638ed13b7ac857d24331d9a4684f05d8
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
upZVkGbJgcvN7CkKzXZIs4xQevoOy7q8e60IAEzBegEYAOVIk2I422zTQfY1KRPhM/FzRKygmIrTrvsOh03eDg==