why1 reason
spend_windowspend_window_exceeded
this would take GD4XBD2ZD5WR4KGXBG3UCTTY4R54RI237UHGUIPW7RSYJUOW3WL25RB2 to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 6d477b7d628b8e935fff89f36dd2a652f07d5b3c54c445ee0a82e6e41bdd937f
- request
- 6a407fcd18708ce3a2d61656e9068d61da48d6ca8d001c6d603d2ae5e15812ce
- transaction
- dea4b518f033f81a0bf3b70e9afb869d4b4670de1b4c6fe807ac890f075706c5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39059
the chainentry 39059
- sealed to the entry before
- e10c3bbd0a7838ef42e229d915611f95a45b82fd195fea3df0f77a241a888e7c
- this leaf
- 0cb91bd3beb882f4ae550736bd9ba1501d82df0e169399388a0db123f8e8db64
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +l7dlstEoTBG4IMBrqgcwSVpcOZfJ1N/SUlwnXxV7f/2IVzaZMaUNWntz9pCn8uKR9H1ejBlrI2eHadtFt4rCA==