why1 reason
spend_windowspend_window_exceeded
this would take GBI7GSXU5QFU277LWWJW5DLTF2BPDHUXAMDSMITNSDITS5SAQSQLH2V7 to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 8b99eb8434c223a8ac366292ed359bbec7bfa3222f7c2efc80a1574daa7c9eff
- request
- 3b87ce54204d2804659ffb8a2736c09adb2124ca5b4953875cd30a20c7cc560b
- transaction
- 030f547f701eec8ae2618bf28fdf0c675b486dbdf5a5dc90d6efc1cd282f4ef6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75266
the chainentry 75266
- sealed to the entry before
- 83f500289a34d5f136ea14255d6afb759680173a75d0fd2adae82490f6e7b3e1
- this leaf
- 75355e8059478eef2ec9ce37c9450d43d8fdfe635cfd60446747d52f843d3684
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZQeMmj5ihFEHrAsW1YcifyihsuYX4yBBsb3ivj8YUAeUdXUdeUjuFs4oE/nAVJa8YGbsWe1zlXifksB6zIX0Dw==