why1 reason
spend_windowspend_window_exceeded
this would take GDZ5NTNZBCEJBXUXSHO533XZCGQXE6C2LCUZ4R2RTPGCUALWNHQSUXFT to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 2cb4fa01b9f247f3fd5cbe66bd85bf9ea1983334d2d72e6a283944e660981ab9
- request
- 20c34545853a54ad685284630e0bb16c144ca1fecaa70b9758717652e1df1438
- transaction
- febbb1cf270b1e242616e8474a939bb5f24f9a2ecbd8ed1d8a24c06b9ecbffb4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46915
the chainentry 46915
- sealed to the entry before
- e78f77b9f85c11a68c6f8b3a046357ee299fde89b68d52e1fdfc31e374707236
- this leaf
- e5d9d46c13f9cfdc825c1f8b8261ea09f3349db83e9e875bb57434bee7c7c0d7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- H4sdgMsA7oru48Eg+QvGRKh+g6pVLgtzUp3tHANTA7tzXKg1fw2Gf2HmSttDG8AnbnANLo4OzAa5SJkmQF/eCw==