why1 reason
spend_windowspend_window_exceeded
this would take GBJIBCHYQSHEYD2GNV6ORSTXZBBPVRZMMIE5PKYAD4GZDVI2UYEPLVY5 to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 6ecf85feb71736b84095601e2730b2a7774e2400dc740490c9f9cd1f010b1a0f
- request
- 834d9ca0c82f002862c74689817010943c79b7f05ca0801928dc8b3746680757
- transaction
- a41154c2f11ab20efad65bc2cc8926ae20762b0440dae2f074cd57f4b7ca6985computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35332
the chainentry 35332
- sealed to the entry before
- 7760bd0912c9d637816240fa29910e08f2a6ec5bdaec77688efe804b4ceed6a6
- this leaf
- 950bb7dec5ce170d481345accb7b9f25d92400c96e2c0e333d9de28bf3769eb8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cDeNwl218h7wCMD5KerNrHaljnNdxT1HLBk3wtfRXOGt7iVw7RxJCIdPsKtyFXPyofjtifykWjrUzuw8SeWTCw==