why1 reason
spend_windowspend_window_exceeded
this would take GB7IXA74ZYT7RF3XUEQM2PKSTHN3OHAMEOTTZLYIFZLGITX3XEJ7L22M to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- ffe89225d23db349ab45012b24b44b7a74cd169375e336513568090d042ce7db
- request
- b791187c78ebfbfac31ea69534d4733aba7c7012d82d0a98ab7a71739105cabc
- transaction
- ea99a9aa6c4610f42c3023fa34eca2b9ef33ed5a8e2ead5ef5a3e41f82774c2acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70554
the chainentry 70554
- sealed to the entry before
- f99a27e880bc1d26a18cfe9245ab03a2d628ab239435b0d10fb3ed0c61b63e1d
- this leaf
- 704a6a3340303f4091aed9d18d3087a7ce47a0f0068db023e2b2e4736fca98c0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gAtaby1578j68cOQ26xQpS9coqfQTIRrNeb8MW1DRX5tp+qHWm6XHCryKYh9IVRad3z35aDEcRCzsgXwsV2bBg==