why1 reason
spend_windowspend_window_exceeded
this would take GDOJSI43YYMNUNJ7OVJOKP46EJJE5A5QDAWFLTEB7KQLZSEE76CIKZYA to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- f6fa8c07790e1c7e56d2350e7fed453877fa835e1708177ee4c735d3c62b9d66
- request
- a3c14f71af1d603c106ec46bb4caa4379a77e767ee2f93131eb79b00ff0a1bf5
- transaction
- 3472f8d3670db3d0548869e993b8d705f4e489757d9eb85756af4b11f49ec96ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50005
the chainentry 50005
- sealed to the entry before
- bd16210d3bfb3ff8ee0dd1150722b465f462ff00ed74684e53859d8e028c6274
- this leaf
- c54fd96df3c07394a6e7f9cbb54423f02de8eeea724edc3604e457914fdf79f4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- g15cA3/v5CQK7oCFFtYQHQPKPVaDMT0jt3YcSzwt8+oQ+tKe8qv7EPVN6zGI9D6dB89NN7YrJmCNpAsMeBC0CQ==