why1 reason
spend_windowspend_window_exceeded
this would take GBDSJD6RF4XKSDD22CP5CV5WLPKX77WX2YGF5DGCLYABQH5S7EI3ULYY to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 8912b7f8ad94a977dda28be08ecd4fa7166783ee2e129e6e8fd7e06929d0021a
- request
- 3eefda74c286f19b7d3356ee2335b020357625bc108cf0f29e26b69d9e2d1fa5
- transaction
- 8fd87face6f28a2527863f0b904da37492d4d5362ba483a046226382569b70f6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8085
the chainentry 8085
- sealed to the entry before
- 6174389bd26ebafb89d67a0ebbe8fe86893fa58e086371f50fe7ff590605f274
- this leaf
- 37bdeda92709564cf353eae413726113950cd69769a49cf695137be419aac2f4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SAwXWMFWv+qHqbCTprxlZlVfQUItm7GM5BY++QOcY1+CJn6y0bxGIyBKR1ub1BIj1ymY4GbgHXCAwfL3bhl1AA==