why1 reason
spend_windowspend_window_exceeded
this would take GD2FZSPWTBI2ARC3GH4I2JWWPJY34KBMA64NNPJZF6W3ODZG6F74ERF3 to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 79433f75f661611d9e40cfc96108d44b698b8dad21f8e6f132b99f4a55ec16b5
- request
- b2f10ac744df2f9be5f866ab9c73cdacb211c18bb4e97a4cf7a6b8c68484ad5f
- transaction
- bdd8d640a8af618651e6a18eeb43b4398ec247cb1914b44ad5cfef30831e680fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7166
the chainentry 7166
- sealed to the entry before
- ed4dcfbb88690af70a7eda4f0f7a07ce122769c17205eacaa19405cf7bf28018
- this leaf
- b3a10e095ab3ee40898863db54c6f955e4f3035bf7e81f037e376df3d8769d34
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- F4qWFAP0o4p7pKDv83HM/Yr5uDbJgpxFbVQ9l6uqELLYJfG8AZHoN8Palxm+T66t8VVSAqzevXH/zT2TFE8aBA==