why1 reason
spend_windowspend_window_exceeded
this would take GDTPQ2GJQ6XW7NQCI4ILISTF3T26P5F2UH4S66AOCAFHJC7SEK4LGTW3 to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- dbd884b77297e4f33226bd48a94c3d036a482214a41b8739ebc1b77be7b58e37
- request
- b84e154fe20c50093e32dc2080882d04bc6346af4327e1bf7c85ced9489e2652
- transaction
- 6df0e8c38bbd6ffe6e134ce2f298dfd7e2c1c7eac8aa2fa0aa75ed4b7cdc9143computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32648
the chainentry 32648
- sealed to the entry before
- 20574421dcaa25163fc8608a9e881cdb1bbe03b79ff68d5d6c5a1cdca8e84674
- this leaf
- d81acb5cf748b5dcdf2a8f0616bdd233a64526c75a6b4d87d1ec25df5c996ee4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2V3ftnBPfLma2xKidtFKBO3qSJE3P5o/RCxtsc3xWRjHCbFgKpKmoXNkkTGjPsc7Ck5qjSb4ZWRtY5lmUkInCw==