why1 reason
spend_windowspend_window_exceeded
this would take GC6UFI2XNDWSOL7CQ4PRZYO25T4RPEMTD4IGR3ODSMVAF26FY23EMRUN to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- b303782fa663a929ebb2490c4ecd4d10cfbaaf55cdfa566dff38c900c6ebc590
- request
- c0ce1576fdec119f9a0e36ff6c17585c5a63169c6871987c07a3a1f60c72697b
- transaction
- 6059bea59e8bbc3e96db1714fcf0e65ee436a2aa72f34ad068dffef71b334d5ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51086
the chainentry 51086
- sealed to the entry before
- 8ad83563b329e717df561eb2cec6f952cddbdf718df8128bc537f62f2718b614
- this leaf
- f896a126fe456575572ca943b915bceb278163f66a7db4eaa38782720c065fa0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pRKXazUACVkJ1pNprHOTvVjEI8cIoJgEIGTLVKHJgqgHYEmyqYhTForVXvAdFOfpui5xtnxWckUyHf92aXjqAQ==