why1 reason
spend_windowspend_window_exceeded
this would take GDQBTY7FG4JCJOI2FEVMXIDIU37XXIRIGGFIB26FZ4Z4RKOUEV2R2LBG to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 8d665e1c30aa81cc3465a006eb30713ca49ac06b1c1fefe1ac31961ba696b3b2
- request
- 7fe66f1b95286530644895e94c87a6972053769411e31c080e014ac284bc11d9
- transaction
- ec5107bc8dfcf0f58d3418db9734df1cdd241e3b51f3c6daca49fabb887aaa3fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67651
the chainentry 67651
- sealed to the entry before
- 54688e86fdeb1a9e410ace2eff788f73bad6fa64ab9d422961821ec4ef8ad246
- this leaf
- cf9a929bce5a480994fcfae5599a41681e708c9a79d85140c0353d64805acbdc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GLDFGVDsrMCid1lBFO4Bsnh0/M6FYrcmBzPD/xxXmSdyjceOXI8tVffg4HGc3lyMUr5IPc1zSSegunVCe8j7AQ==