why1 reason
spend_windowspend_window_exceeded
this would take GDQANT5BK2EYD2XUENG7ZC466JTGW5SJVTN6A5O55TPB2QDFELUSM4JU to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 04d5d1011d12ac00494049fb0877a0b0490a125ce42546c76c05a1fe3fd1bf51
- request
- bfbe6a4778a3862c2fcb6a69b2530b23c975e3ca25b75ed7e1e1be81270ef2d7
- transaction
- 233db22ec12e7ceb046afa0afadf50aa1e225c2444e90527d4314222d5d8d178computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44641
the chainentry 44641
- sealed to the entry before
- b8b96caf933ea7342b9ac4c0ceef0d3e9e654dc7429cba581a27c569715d4336
- this leaf
- 602fcc145177091b1cb342d65b6c9c11f803cc323c55fd03166b963c0ff3071e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6up9aXIcDFvk6f5j6AmI96sgagT2tRdyFvd+TgxbLbW+ArMuJNZD+qlPXzPtrbQLE1ZgRcjYcE/tSqsCJ3LWDA==