why1 reason
spend_windowspend_window_exceeded
this would take GBMV6K3WFTTN7ZWLVEF7VKGWHJJ4VUT2K5QS3TGTW2TZEXDJ34RL6IVX to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- cce84d94be38aa9ee322b5a19d97ece928b2837fbf36bf2053484530c2fe286c
- request
- d9f96df67905531616161daef710ffd09ea1fce5ce5ad7ada3b5f6663b07f41c
- transaction
- 5f7e9b88018b705672c28393e46bb531b1471fe7f5032bb8483cd67627c35f78computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41705
the chainentry 41705
- sealed to the entry before
- 4a909a7821b6b291e307a3ede8a4eeb8b45bf62f1561f46685430177ac6ccced
- this leaf
- 1170d7d71f3b73dd6c548238deeee4ad0a936c6b471a714b7f3f7b2412322514
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- B6D2RFRYM0hw9I2uQFY9fOOhHZGINa3XMc4RIJ9ySkd9pH/5hBJOH6/xeXvKIWDgPOPAOFmvBX5Or2B+MldGCQ==