why1 reason
spend_windowspend_window_exceeded
this would take GDIQPWINUPCSCWT5UF3MWREX7OZCYDF33KJZ63YXJP64PXQYQTKY7JOK to 140 over the last 60000ms, above the 120 window cap, with 70 already spent
what it was decided fromfingerprints
- rule compiled from it
- 9ce1a07356f5bafbe7e06beda3b25a44e36f0eb59e4ed5ba8e12bd09f2730d40
- request
- c9893fabbfbe8f4aea5406ec3c9e97610ddfd1ce2bfb6ea2fd140dcbce1c4c50
- transaction
- 432e0a2f7ea9d0b58a046c6cdbf841ae43168cc48c6038a1ff8a9b1ec0e75f00computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7
the chainentry 7
- sealed to the entry before
- 9dba4c0ec8c86669d0cbcfd20de1a0eae185c869803e697cb395206336b48462
- this leaf
- f1dd55355bd692afa4cd5610e649033e9c1238408b98925f3ef9a791aa453f5e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- k0EdRCb/B9h50z1xBAcYReJJvVwoD4Q3L0m0xCKZqow4arQqus4mNa5lgxn5aa23ntd7xeJVG/W+fBBBcJdJBQ==