why1 reason
spend_windowspend_window_exceeded
this would take GBQJX74ADDC2WSB2WLELLVD65AQOAD5ICNPA4P4UZPJ7RD7QA4O3L7XX to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 9d775e3ecd6937212d798d9b0da859e5748abbc4f0d5c660e74913405b5a27aa
- request
- ebef3b38f93ff701306c2a5a8201912396e27984b25addd60e45dc61e79e6499
- transaction
- 3393eb409db8f2f44e3d8864b73319d2f1eaa911fca53f244d842d0e6d4912dccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3368
the chainentry 3368
- sealed to the entry before
- a6ab34608e68bf141b596382dd54364c0daea38e581d54cd6f7888ba4f9292e4
- this leaf
- 2a1e7051d5056360688b510aa49a13b336efb5b91a50d5c0e70addd07ba9e0c7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UXudiA/mMq9pt4eGJh53blan6t/DaxcuKLY5Oqk41EbsIpRaBGWkfJxJw6bNW3r7OCR37OWgu+m25X0MSywuBQ==