why1 reason
spend_windowspend_window_exceeded
this would take GD7LYGLAKXS2EWRLH3I6LNLYB33E6OGPTITQWUIQGPNDXURYJJTPUTNJ to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 98d9e2f4c6aaf54a4be3db02ee8edeae61cffcb39bef4d84274d8430ea5646ca
- request
- 811797c2e8ceacb28feca14712d7812d4b4c9c3657560e59821b56614eb6096d
- transaction
- bfc49899c7bd5ae7614543d174ae386b0d54963a1ab78ec74773727d3ba27d3ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69015
the chainentry 69015
- sealed to the entry before
- 13ded23918750b6f2231dbdd65f325163bef0aae4a134cba93b8e9e18ca18c45
- this leaf
- d68ae4276906d25c023a0393b5cc77a8e7c81472aea64c0cbee11e3edc745fa5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- b/ZlNdLXm2rUMuaO4qvHX++zx0FklT3wB77hl2evy7P2vyGtQdCVNdfGEKj9ThztdCw1s9BUO493FJc6G+n+BQ==