why1 reason
spend_windowspend_window_exceeded
this would take GD3ICNMC33MAJJIKNJMADDINXK6QUPN6BFVD3FA7KJ4H6HZ34ONCTNRL to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 4cc5598cd49add12b36a2fc8fecfef8aa1fcdf63bc26945dcf1b0a7cc4e3e7b5
- request
- 7b97cfc8d1bc986efc5f4d1115c7ce84b1862ca643c2702a6d082074b9e2fc41
- transaction
- 0c0681fcd72d8c7de12b579bc599f5c327839706714e615723bb5516de7a924fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11841
the chainentry 11841
- sealed to the entry before
- 84ab61262e34a49747fd1f8d4af5d9d19a00d97a70f5a8d09bfe4310c9899b5e
- this leaf
- 160633cafd18a6ed5753b117079b4ee5b254ff6e1e8b2ea4c919dc3328f5069d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JUPAMqXGyvOG+dqyXh0T+qbo3+QIONkCbNdsrRK/fF0RSOLZtGcIgjXo0dT/e3M6LwqoD85apHlwu9PcPj9gDw==