why1 reason
spend_windowspend_window_exceeded
this would take GCC4HMREOYBQ4LFYW273U256EGM7KSRCKJULZVLHQLDXAILZRM5B7JUO to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 8f52dbe16da4c2e0778c9334d83b5ffd768c10d2e70cce14b00a69b98abf354b
- request
- ee825f856dc264ffa94e7b157410fc0b9a295577968e182245c12dc74aca3fd3
- transaction
- 6be421ca72969fe12ea00336ae06502b75df0bad423f8094b6db3631dc7d633fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72169
the chainentry 72169
- sealed to the entry before
- eac735de98bad06241e37aaf9c364d205da26fd77c86fed02bcda811194d768a
- this leaf
- 41776688bd044bbeeb8f9beefaf83daa6651e568bede245a9516a0474bc27e08
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TX9a6aSWMI8QRmQPzGMQrFNeXvQTURXbdYEYbIrLawPYWFoO4wdVhYpYJkezYjkREngTqQ3DbOwXSX2J3cyjDg==