why1 reason
spend_windowspend_window_exceeded
this would take GDFO7W7S4MIKKKEDUHNA67AT56U3DFXGQOXHNA4HM546BDHADB6TIXJC to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 9a935766db4ff8c4afcd2aa76c2b1c356eba67fec95436b10b65be49e54e67d1
- request
- 3ccf5f92174e0cf20bf4223a85f01142f7ad70984e0ea1fe46e90397efb6ab6a
- transaction
- a872e07636e36c1a09021382a4605c2cf161a8024bd460026ddd77f53ccec974computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20185
the chainentry 20185
- sealed to the entry before
- 76922e69d8845ab98e0b9f6271acdf0da9c27f8af4c089cc95d05ac967fb21c8
- this leaf
- 9a0097ac7aa31adf2b64b59ea88df1e0a541c81433298aa9a0d78bcae2a97d7f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jQ6+qzyxcIVqgtzqR1Fkn+MQn2i+t7SiAYqKIHFyOj0/390f23Fi99IQq1gu56LWb+pbP8/snezfJvRgrDkCDA==