why1 reason
spend_windowspend_window_exceeded
this would take GC4P77BBU5WSNPPIMYCA35A55KJ75WEZBHFSNTFO4O5M3RT4MRTXBZ4C to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- 6d918423d2c4030e1836b1096af78a41831740812d1fe7f56646015b23f30c90
- request
- 2dada51366a9b00577dcccd8b253b4a7cb7cb32ead4d54649e7338851a8dd3b8
- transaction
- 7c709c0a7ca0e63d04ba73fecb6dafb630be7541a1dd005c5b1bb5b4f62ddee3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27411
the chainentry 27411
- sealed to the entry before
- fb87e5ffe5c26b893f1dc2b644af3a8fd4184ccd4b926364d575656a5cceb443
- this leaf
- 5d92484c491de8964c6b3f5dd55d2db49c3de097f1e032ba93d6ae5f80b38e38
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8dOEWbrOeSWVOSmQxUfDNxJboIex+/jrdjDQNzS25XEi4fj1GbLG1uarr3mkcOb/nQjZtPSMZU1Ko8usibM8CQ==