livelog 40,994 entries · root 54a1a7488551 · read 06:35:38
the record/entry 40846
DENY
refused before it reached the network
op 0 pays GB5BURRVQEGFEOMQ2KGTXZK7QNQN3IP5CMJQV4HFKHOACC7L2KNKXBDC, which is not in the allowlist
decided in 7.139ms2026-09-09 03:50:13
why2 reasons
mandatedestination_not_allowed

op 0 pays GB5BURRVQEGFEOMQ2KGTXZK7QNQN3IP5CMJQV4HFKHOACC7L2KNKXBDC, which is not in the allowlist

counterpartycounterparty_denied

GB5BURRVQEGFEOMQ2KGTXZK7QNQN3IP5CMJQV4HFKHOACC7L2KNKXBDC 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
55b9ac6f98c779208d9c4d46b84d4638a71adae88af1d2e785ffa54e99d5cc38
request
12249139a8a37624b73a6658d3b3afc78425608cf0faafb79087f11772b8414a
transaction
da7ad76bedc91670775f3f474dd70dd0d3eb2a54f2fdbc09332b4826485b0f3b
computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40846
recomputing…
the chainentry 40846
sealed to the entry before
d4d40fc1e7beab33031ee339c42cfe8b01e130088a7b4cce60b7f0f7e3838f0d
this leaf
57cf5d9844c152bf210a47b0d3db0dc1fb23046cd5c15aa707732555c6687ee5
signed by
GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
signature
grfhnN4PMYG4QdCU9V7Au97pqXmw2I4A6kdlu3BCFLaAR+6kWsbcF5NiEkna4PSzYlASDD/kFYzea128daQ6Aw==