livelog 15,783 entries · root ca61589a08ce · read 18:47:34
the record/entry 1054
DENY
refused before it reached the network
op 0 pays GCU3JAOVR2YVCVNLDS7E3M6MD3PCFJX33PLUQ5BYFDW7W2JRQETTACQB, which is not in the allowlist
decided in 6.622ms2026-08-09 08:36:14
why2 reasons
mandatedestination_not_allowed

op 0 pays GCU3JAOVR2YVCVNLDS7E3M6MD3PCFJX33PLUQ5BYFDW7W2JRQETTACQB, which is not in the allowlist

counterpartycounterparty_denied

GCU3JAOVR2YVCVNLDS7E3M6MD3PCFJX33PLUQ5BYFDW7W2JRQETTACQB 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
43612a8ea0705323395de88865dedfc437e688d2ff751ba924ccb9a16f50314f
request
f30679519244808086220d969e6647d1bce1a52811ea023ea5f32f2ea59d816a
transaction
e3e9da641dc6b231b32bdf27e9c7c7ccad988e19370a2b31b5cb1fa46691d67f
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1054
recomputing…
the chainentry 1054
sealed to the entry before
fad59a8b33eea91eb3d2a21b75803134a5703ab9563b85ca1420915837aeebd4
this leaf
7780cfc017dc4729e6054d1f01b6e09360c6eb50bcde4264492c7417ad766688
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
R34GVP0D00G1IVwGhxRJ0PiI9azXPt9/OJUIRekhhEl5zvkqgv09YQVJsShP0s7sOxR3NGVOzfUwdQYUdRqsCg==