why1 reason
spend_windowspend_window_exceeded
this would take GBHRBMTWQCKQ5USJAQ55KJW4QBL2IUSX4SAPOZ62M47DM55FXBICDFQX to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 8e6249a4265053850f843f4412f9f2956d3f056eb547c4390f639e5d91ccf788
- request
- 0ff85ca646694f0f4272ba1ca9ad8fbdd69a50499bff7030b6b88dd24f01fb56
- transaction
- 249134f7a6de47512977fa5fee6d300f63d5f14ce5ad53465a7490ad50f0a29acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26572
the chainentry 26572
- sealed to the entry before
- 1db0264f69c25614b3414b2f8f752f398de5319585f6b223368c9a8a5e1ba53a
- this leaf
- 790b9b9dcb1d470787e556f90d729fadb407ceb8c482eb1d52111788f7dc0ef3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mNiL9Oq34QUXVKtWGNnFAP4+STIMawTnF77UsXvxWIuP594+5ADXtUUzfrOWIrFQn5z4JzMKQY1jXTVbouMTDQ==