why1 reason
spend_windowspend_window_exceeded
this would take GAQAEL5BGO3HXCF4BMDZXM3OUICY5GEJSVCPOPYLI3WVY3CIQ4QQIPEL to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- b888ad1baf11f532ef5e27f8edfa0d2505442333e603203b56a7000410438733
- request
- 72d0d80a50a4496a1a076100c248f0aeb9f9ff0b6949b1da976c68fafceaaab1
- transaction
- c1cb122fbe284944a4ea6e5d5f07680b7ac7515dd3129cf728bdc5ee0534807ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70798
the chainentry 70798
- sealed to the entry before
- 66596ae28fc95788b342c81d5921a902ea3a45ed74f1d95936a6994e38fb1c92
- this leaf
- af9331a6040b94656e0d1af8e368147c7cdbc4ae28b31de6c9e7d3ab25bb94e4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DphYNo9hXibSm7pOk0EoXW+k95lDKX+rQKcr+jOJJ3LzcGORLkY4V5OCQaCfjDYviYCbFP8b8lmUBjf0HfpcBw==