why1 reason
spend_windowspend_window_exceeded
this would take GDAU2BHGA6CD5QOVRIIUHVJHHXUOQ67EWCGYY5SA3P53NGWYACDBNCPO to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 2e118c7ec13a86ccb1b222c1b9b642f26f3ff0c092e75ee718dbddbc726c5cb7
- request
- 0007a550d638a1da434813551ca1da0ad587a9ce6abd3ec588c5087444e85b0f
- transaction
- 01e6da8db910bf6ce1be11c16a0d99eb2c1b8b14de47c44fba2f3f4733726946computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31926
the chainentry 31926
- sealed to the entry before
- c739bc3c8acb1dbb78aa9188a266d09ca0a6cf98f6a9b50cf92c695d3db58f5f
- this leaf
- ccb3a4134e4f6b953159b8e754ca426fff22808a2eb26c0fbdbf9704e64901bb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +/Beea67BXM5lRU+GFeHtgJMURTt6YXyHsyTGpj6AEhynVPV5ypTSzHH4xEurAzz3luqaQ0OlVEmf5lzck1lDg==