why1 reason
spend_windowspend_window_exceeded
this would take GDRCVNWU5GH57FCK3CE3VNOF7GKVJZEEZJKR3U7AIFDB4VJ5KQYKJONU to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- fbc5a0e450d3b3ce18fae54d9b6bc4078748b170ae8651d5644a8371835914ec
- request
- af93c7e576a9d8eb587b76c73b68e9f7ab79a239d65f8ace9efffac4f41303df
- transaction
- aa27983c8fbeed6d170cf52c7ef330747408994751ca203fa2199bdd5b4f7bcdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53865
the chainentry 53865
- sealed to the entry before
- 2b9909f0c57cc8bbdcb5c53a64ee2be2069fd2e5c83a4b7f6c13f432f0325043
- this leaf
- 8e2ccf140590caef2803a91879feda1a66ec5585a5bb2bedbc8cd51a5976e680
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IboGCcZIavCLszvDanoKkx69gU+hNLeIqIhFEAJmS/HfPxEKzPt8z+Bs11hY2HVZL2laoaza926lQdMPVM3GCw==