why1 reason
spend_windowspend_window_exceeded
this would take GD3PK2T3C7LWOTJ4OC3HVBP5R7LO2VJBBSBT72IDCSXKZHQ36O5LI6Q5 to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- e1edbdd9237211df1ddee6edacb5cfa5a65ac349184a4cc66de41e7b88446c4d
- request
- 938703267946113f4b8e68b58b1f6ef2e5b9ee7b29a8003c16e707584b86469e
- transaction
- 1c63017585eb65da684348bdfc0f111f45a67a3ea2e2db0b76324ca080de6bd5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26114
the chainentry 26114
- sealed to the entry before
- 2b3615674e3f7af193a11a19ea480688073f89200e437d3376338978b526b46f
- this leaf
- b6c10fb1fd37fe29068e64abd3939956f1e283f815d13a61230056d455e58445
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6+cTyBG62aG2qWWJyOR3oF9nS816fY9vFmSP9J5xAWrELDTTj647oMFmfFXZwldg6hGqIINeb0cddMvc3oecAQ==