why1 reason
spend_windowspend_window_exceeded
this would take GD36Q6D44BLZPBTSIACIL3GLFNZWUEFWL4P77RKMEN5K5M6FFJXEJYN6 to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- f0463714915b82503be0508085266d25c531454079e80d2efac4288ee2ecade3
- request
- 9ba9031d2dd5b17869d8c6cadda1f48e31c042403f7284c6a021d84fa17ede4c
- transaction
- 7b6b8e0152c88f6d1c93b337a44234b9dca4a90f55e8b4ce63cd234caa4d0c87computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29152
the chainentry 29152
- sealed to the entry before
- 29cd60dbdfb339dbef168d504432bf1154194aae544919f35b5332f8629a9b9f
- this leaf
- 63cf8a3c580d3fe0fb98f7fae85d2c4e12a94d0abfb13e23332aee6adf2e57f0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Pw7zLFnw3s4I6FwjSNDi9I42RbVApxiGgFvGEOr9q4LKP5DgZRk2vmA7fCoiH80l9ZELaNtbP0MbDBhT4AHfAw==