why1 reason
spend_windowspend_window_exceeded
this would take GD4SOQ2HVT5NR6QVM6WO2R5U7K24QIOQZLDOQOTGNQBZPZLM6VU44CQL to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 76a426294c09b8c5b2cbc6cf0a5dfa6e1b02b8ce93bd14b779b3896c2faeae57
- request
- 4f2fa3fc7de3e0440d27cdc704e2d4e1ef1b93d5ebe4bddbcb0f354576a71ab5
- transaction
- 75570e098d1d4027b512db8bbacd163670c954c6d39ba1d90d67db580adf8f93computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60682
the chainentry 60682
- sealed to the entry before
- 069494036c199ed95ba41c9e1d0321eb7c523bb65a27561f80164a97a44c4e8a
- this leaf
- cc102bf4427a57b05309d02f1bc725afba8ac5bf512e7aebeef0ffdbd30c63ab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0iDwGWF+86u1Wv+a24Effk/lDvkP5/a2AjUoeW8xd27valqf6Kq8nIg9WPhuGqeBvhRHi30Q6j88AUTwPobKDA==