livelog 52,421 entries · root d8cd0b92366d · read 18:30:42
the record/entry 51037
DENY
refused before it reached the network
op 0 pays GDVVAYMLPPKPMJLGX3OTXREFTEMNWQQIOYILAQBFCKGLTL6TADV63BP6, which is not in the allowlist
decided in 6.688ms2026-09-16 17:20:15
why2 reasons
mandatedestination_not_allowed

op 0 pays GDVVAYMLPPKPMJLGX3OTXREFTEMNWQQIOYILAQBFCKGLTL6TADV63BP6, which is not in the allowlist

counterpartycounterparty_denied

GDVVAYMLPPKPMJLGX3OTXREFTEMNWQQIOYILAQBFCKGLTL6TADV63BP6 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
0fd98de6c081449f853c08c642dcedf7028be7d6d6d237af52a4645a1f65b347
request
82942d132205560c5275bcf31c687490ca409d6f5cd18d86c95eff5c317b27e5
transaction
792e8d8653d175499e2e439ce1fe34be637a5dd1a464046e3fb3e1dce746625d
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51037
recomputing…
the chainentry 51037
sealed to the entry before
5354edbd5e0dff2f8bb91a90cb3ba29ffbae80f2c1340c25047dd284719de636
this leaf
8c680b677d31ef052414d706b9a6586bb1ce0025f363f96db292366dca2892b0
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
vpub7lw0YxgzOEz+eLsMc8WFYraXzYp/fr0KNb+XMY3GP4I5V9VJ+hZUjO2GhgS40THBkGs7TrcdfaCFBwEvAg==