why1 reason
spend_windowspend_window_exceeded
this would take GC2WO4DYN5XDGECREPPGAUQ7A7KKACHFRLGJ3GCIWAQQWVVMBZ5MTGU5 to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 8a3bcf03b7821d53a2a0622b7ebe92e591854c33061ef44aacb14e577029c369
- request
- ed650223b0f28db0e0310fc8e2d9911e4be3455b7750f102278c38b10696abcd
- transaction
- 38e05a795540f65c8ed0ebb7f33b75d0601e1e9780da7aecfaedef8b88d6d262computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33535
the chainentry 33535
- sealed to the entry before
- 29b24b0dd8f2a24e4a9e15ccd638979ab48d2491e39414e2ea738020ea1b9eb0
- this leaf
- 960303016cf442c939b1a05c96ab2f221dd75ec5d0b1b9b7b1b04344a7fa2148
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- B0sDTwjGWX8VZ1aMI5aFGn0a3wkfaZM+3E5xVK9+wpVm8uvpCWtyfqUC9xmSd14jBbbZooFXDAv7IVzi5m4eAw==