why1 reason
spend_windowspend_window_exceeded
this would take GAU4QDONGTBKPEVU7IJFWGFAERPFR6NDTVTCJ45AZN4R2FDTOJJ3T3RL to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- c9f990de1ea84348ecd2e0fee90e02c897ed9ce5d28989fb5e88974c7c79d647
- request
- fb6acb58e4fba03017dea58a0595e55254504200a8dc11977a63b818392cc63c
- transaction
- 8b179034a0692f6195576c284d6f9c649ee2c0e6d3bbf69b3d07543d1c7ed724computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66200
the chainentry 66200
- sealed to the entry before
- 112f0ea7e4ecf3b887d20a71aef75327efdc778e62a40b02216e173aea9aa911
- this leaf
- 55d7a71f95b89b376a1d2cbe23208a21afd5f4ae718aa011099c3e84d0aa9e3e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZEEuQHp0kTgUnG/pw9ojPr+cHzWf7/DO2ex45ETwCzUMYip3LAjuWk+2gIRjBtJTejZnmC03fUX1Bnclsc7VCQ==