why1 reason
spend_windowspend_window_exceeded
this would take GCXQMIQ6WXDRETDIQPQURLXBPZUN5O24V2EMX4TXJA3344WZLAVSQSOK to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 6b3624a92c562456f48c6e4d5ade4ac3a868584f478e4e9037e983213cf1f1e1
- request
- c852da48707efc155594b92d1a950dddc4e4e412f360688fd549b668bb36ab81
- transaction
- bacdee01f2e80f6a22c05b410bc50ff2ec8be670cd23dffe23c67cfec1004b54computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23028
the chainentry 23028
- sealed to the entry before
- b6c0cd84dab4fdc93f884ba4df8e69c275f745bfb3f33d8e742190ae7d0f5994
- this leaf
- ff87599e7ccb3eb79dd88088a9a0ad04c371cd2880b2ae6e7cc8726e5c524563
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 14iAF2G5/eHYyk/prL07pRqBzsPTQjoiNOqKRJ0E4CmaNc20dHIvgQ3if24JK36eIpX6z4dNIk4nTnQcMIA+Aw==