why1 reason
spend_windowspend_window_exceeded
this would take GBXTCPTE6WREZHKTW3I4BUIJGBFOYCU5DI2PAFLTUKD3DVX25TRCS5ZN to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- aacd72ae1fffb13067faf80413af9f7bc17909c2ecf6a55332116341140c1044
- request
- 8d54e229bcb36e008210685b357a34dfc9fa8fb7d0f59f469ae63fb76784d7e5
- transaction
- 57a9c84003cfeabff127b4121a5f1b34ecf3910c1dc6be424d997c0930b3c78ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36015
the chainentry 36015
- sealed to the entry before
- eda52755c26db6c4a11fcd7404f505b913a5dccb4bd8c72b14ddf30298f30800
- this leaf
- 2f4d7d3745fbd6f42b7db8ec4522361e854a9720a42b7e9671d8487afbda1ac7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /Pw6mnKWxQ2W/hT1wV23K6NN2sPIeJJa96NeQSuMAezQsjPdOUnsWP0cAzJjPFdKVw95dlsVTX6AK6P2Hk43BQ==