why1 reason
spend_windowspend_window_exceeded
this would take GDP26CO5P3E5LCVB75GIBR2TZP5I2CKNJKIUO2UOKFOQGSKKIT33CRP7 to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- ec06016bcd086f61e3413ea03e803f11f5b55f9247503d115670320b3126d9c6
- request
- f7e567112d60bc5ffcdd301058fdf5ff565267e113586a289bbd0c4e6ea22dc5
- transaction
- ecab653063c2a97176d71bcdffdccc0c0d153671cdcd0fe885ee0817f971216ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23186
the chainentry 23186
- sealed to the entry before
- 0e720b9182cb141a61ce17373b45005347e8773a5f1fb6f08bc505e4cecb3ee2
- this leaf
- d289d7012040722c501d5943f1c53707f709767e188d396ecae6ecf15c048a1d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DBoguFseKwmQuecP/vKolQe28QrwOpJX/TvJmzatoeaG/VKHuKAyTzuNPfHu73/ZYMjm8qEYxRQDP94fxMUaCg==