why1 reason
spend_windowspend_window_exceeded
this would take GDQ7FDQLTECKKFZTHSEIXPX4OTCPRLGIHYGWWV77FTBSWODTK6GWKDY3 to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 03fa4d452e9524ffd6b243e931b29c4da3dab70682fb6551f6cf68c8e12d5f3b
- request
- 1f14d85b45870aad718a6f1a73ee262f92cd9ac137de27d3849dbfc6bf16155f
- transaction
- a5980bcd3083a953d1306119ee32748b88b914c180d099fdfedc542afd7592dfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9806
the chainentry 9806
- sealed to the entry before
- 4fadfb7adf8ddad40b6e53d9bbc88a0c983bf9f358e9e94784583b1d0a7de0db
- this leaf
- 60629a5dd6c848ee83b5798a0943752939df9ff14371243c4eaa0346ef44a31f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oSnakVry31Ax3b+sGWySeNgnb0cptfh4+i9dMkNDMs3Yphn2uy9tRPH0PbiH0QVHbmGn0dtyA+MhzMtn9THGDg==