why1 reason
spend_windowspend_window_exceeded
this would take GDH5TL2V3I52JRBKX5MW64LOOVTINKRZKGZBMMXDSBAZH46BN5BRTZ34 to 140 over the last 60000ms, above the 120 window cap, with 70 already spent
what it was decided fromfingerprints
- rule compiled from it
- 0c850eab486570ad394ece35b6ca2ab7de95fd5f64c0df0ace18fbc1c44fc038
- request
- fdd4c4f99f19aa107008c33b517a39e9843788efb5d706f70a5d41e9a9ac9977
- transaction
- ea0a4f5f5267cad3c9ba9a251eb9d3e712dcd3747b8b9d2982c47d550213638dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13
the chainentry 13
- sealed to the entry before
- a27ae2baa16a92061f9090f3e93ec0bf1bacef5dcf12c39625e2672437766cad
- this leaf
- 34a277bbb575ed74a203b90ca9f647d5552c5bd693d87ab90aafddf20e13c5f1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- u9sl60rIfpgoVuYduefvYghONaC0S5jbRdKc+kKrHJkgjZLXMZIbSv7sS20q9L5Wc2Wbs92oKyaPc2sm9iTLAw==