why1 reason
spend_windowspend_window_exceeded
this would take GCCQG35DIMM24JSLIYYI2TGFRBYCY5HNN4TGO2VW3YLXSJIO7CCVMUBA to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- b5578ed6f3d6bc0fd9bf4b635aeda667bca98efc9e2fef497b85bfe3186aaff4
- request
- 8f767fbb9846e35dfe5cb36a8d3d3dd33d9fe5940101c25c5a55707a1a22dc0f
- transaction
- e4ce48b1cd76953a473e3a83fea366b17398c555e57a5831830b6eeb1aab335acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42973
the chainentry 42973
- sealed to the entry before
- 47ad0a584b44541277e5cfa09c84e7c5cee2bb5a8e64d53917afe16e558043cd
- this leaf
- cfdf24c40e0a4ddd7a2771f45c2dbefc18b0c022ee7c95046056ac707a76f0c0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FzqtdBMC5gTgCktGt8iN+G+EPYZu1a+W10EU90HIbLDMdWMd/MtE4Sl+qzlO88su5MSs2iL3/PYzU2CdlFaCBw==