why1 reason
spend_windowspend_window_exceeded
this would take GD4Q24QUBLQRTSCYQ4ELCG7GZMH72IG7S66GZVCVTVPIFHDH26BULQNS to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 822da6141d541c0d9aa64e80b107097bed905b1648101c9e8a31fa74fb0ec44c
- request
- 8d4deeb447341324349b3784f7cfa443be59db9fecdf99c5987d6706294a7a87
- transaction
- e781c2432ef28c7b00b341bb23fad41085b380e9a22a97edbb9d7644bcb595abcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7648
the chainentry 7648
- sealed to the entry before
- a9fd1ee189d48a7f847f6625b2d90071f1b0506f43799a436293183d9132f0c9
- this leaf
- 7c5673205c450829fd0c36d5a2c143da8cfbd7b6e889f60e87516a67cee78f1e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- v5Pe/4eKVnIVF9I2G9JIoZ8pv+nJY5sILyi7d0PNDitHNSM4O5VWSEJITYMbBs1v7yXeGEN80hhV9k1mNOg8AQ==