why1 reason
spend_windowspend_window_exceeded
this would take GDDS7V3DWW7QS4PGE75UIQGACSV3UXCY3CQTGL3NLTSXVVPCGRYAQ7S5 to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 32437211d9cf8052755f821c6d41fb79af16f3a318f2334fd14f905253acf570
- request
- d20ba8aaaf771403ab7fae1aecc9bcc74d9d203e478d2b6024c3c75bccca4dcf
- transaction
- 1ed00610f0c10322cb152816dfe102278d0196d28b964dac3b50b99f83778f09computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45729
the chainentry 45729
- sealed to the entry before
- 0439690f854f28fb8102937139a5abf6c65db74b80cd372e6e140621e8af467f
- this leaf
- 4e1489d197ca45ec3b3fd1a4e2ad421cf75b8111cfb1b8d340669bc374943685
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0OrDKiBESzNVtROURDutGq+y5Tf8Fl9ptwrxS6xbJEHTjT+FcD26qcgJVMfsKGivy9vODm99LopPVZoikH7+Dg==