why1 reason
spend_windowspend_window_exceeded
this would take GD3XZKV2NNI6CQLJKDJFLO3FJAXP4LQQHECMZH7E4H6R2GPPGM44VOPH to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- 6e6abd3c239e2ab1eed0e05e2f308c5ad769165ce15f9d3c4e76c70d327f291f
- request
- 161f3186bec265d88eead77aa2d38cac8616502390fea72ea72bb019e3a2bd9c
- transaction
- 24931383142f0a70def20fbc1f7a6345d360f933582057ab35dc1470594a1dc8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71997
the chainentry 71997
- sealed to the entry before
- 70de2babaac3d27ada20a34924965e97ae550789352c264deef0f5ed8ae32c41
- this leaf
- 9436cc994f76aafebf9095ba3fbea8d9f75bc936afc2412b6630d2476fa955ed
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- V+wBwH4DVmt/cAkAXTvMxOtg991v7iRs2IE6RNaOAJlU/xn/ZIQTPj71bvQR9BCKJiW+sttURVqhzjsJYuIIAA==