why1 reason
spend_windowspend_window_exceeded
this would take GDCSGNRUN4EMPRNOGWWLUWCS5GK4JF722K5KOLFW5RC3R4ABQDMRZXRD to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- b3d2e9ba3a1824e2e4ea15597378bcfdf923d5b21e6ed8c6d9730bb96e34285c
- request
- 4ad02586e4b413169edf53a024c9a6671ad13c81059142b056010160defd7210
- transaction
- c95d90b97335c16dbe0b1c83242f03aebc280756fca4a57714379efd938518b1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17477
the chainentry 17477
- sealed to the entry before
- 33fcf382f14788af05042e0a4dc58813b8e67999972def9be238ebe128a756c7
- this leaf
- 3779925c4170e5aeb8b888539df7531e9e3d80d0fee9f7d98156c54ee834f428
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6dq0y4HefbEV8f8BEqs+TDYgEg8vxDz2ByvZHm4N/3U8dpf4DCF7DNK7OODI1HK2ds+Hm8yVIorajC/rkkugCA==