why1 reason
spend_windowspend_window_exceeded
this would take GDZJDXE7BKZDISATP62KS36CKLFLKEQWDKZSVHWHDYKCLY4DHN4C6SHV to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- c9f17cfe1296326d4c086ae86fed326e98889a0a04274a823e0fde47dc2badac
- request
- 0ace4fb8cb58f73648f8a23bdffb69a03f67587ac99c9727b6b8eeac20a34045
- transaction
- 49c442ab89bcbbde3ec2d4737528f43e6dcf889aae1ef9cfc8e5adfec9735be6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68006
the chainentry 68006
- sealed to the entry before
- 83469a9abd8ef9678032c796768f789aa16a3cf1b44d37a764e417acbd829b9f
- this leaf
- f7bc8b98d31bf8dee869bfea6a7baa95d4cfb0fb4459b779d06e0f4a8ca2516c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MguDt3Ss900VJkRw+pSUtYNuwpksTZS91TSP0QYFEoAv+rF+/AFhkiUX6XyXkPshcADs622wi9PGre6iG6RmDQ==