why1 reason
spend_windowspend_window_exceeded
this would take GDQFTP3NTHQJXA7EJM4QUN3PC7OPBD6QFVJ6SBQVTINI4R7KEHQN3MB4 to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- ad8305c9ab02d405696051c95e60afd7aef0fcf73ea64b71991d974a141bfb2c
- request
- e4923eeea84e0cf76fe7b1aab8f9ca5c05bbc9ffd766846c2b9e4d475dd7ab4e
- transaction
- a60dd154551b40182cd5ac8f1a0ba27289faf15ae93c35aad5b160e3e0e4be2ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57536
the chainentry 57536
- sealed to the entry before
- 98c1d8ee2e9bfdb3b1488266dfc46f21318047aed087b898ba0ce4bb71cef46c
- this leaf
- b02ada5c3e60b66f9ae146294351029f242fd27897a5540e87a47bc6e9614cfc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- W/3ApgU0XTkJhsxB7aIECfTCrwqUGro3Et9EIs8mlMkqU+XyCM7a/Ndn4IjCTvJYsInsLw2KjAUPNyjd0sUwCA==