why1 reason
spend_windowspend_window_exceeded
this would take GD3KNVGC6IBUA4U4MIONKOL4PXGL4PPPBMLVUQGKD2BEZULU26DPQDVL to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- c693d90867676f9290ffe3376e4990ac74035ec27956d0d24a02897f441c0697
- request
- 4348639b898f6b56f183db5e934896c8d265482474e071b6a2fa3cefadbd18a5
- transaction
- 8007542182d1c08398833b5e336e5c6ecc4300556f9e781ce30ea30946d28379computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70486
the chainentry 70486
- sealed to the entry before
- c5e7586b92ebe00287b9e92d53c7a180edc6c1cec21ec990ea3c0c370eca3e86
- this leaf
- 1e24706d2e8cde28a07fab3c38a86efdfe598debf2fe5d822a6bddfcda4ddf95
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Oxc5qzbsgPJpz2+2t5lkbt/iF5FO35yxEu1AUD+sS2q0XHsPkWiDhE0HR/MIX0koQZq4aAeVQPgVyCzndOLsAg==