why1 reason
spend_windowspend_window_exceeded
this would take GD5RYH7BDQ5ER6YLMMAZIV2BCZYBQ6AGRPTUNXAXJBS4KQVDEC25OGX7 to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 798cf971f867df3f3147288eeecdc7e41db0077977eaade37de25c8c7016841d
- request
- f3cfbbc5e9964ec0144a8d02ac352ca093c0d1f6cd7ecbd431f01bff1c71aac9
- transaction
- 1a6aed103225d669bd2b186bb253cd8e9e79e9e2b0f92d2f98c56675b003c951computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74821
the chainentry 74821
- sealed to the entry before
- 4ef47188d1c38ba9e08b19f495075f91160d4e84792e7ad6dab408c10226e8c4
- this leaf
- 44d031d9e687a56122fd50620979b03e2b106c75c04d62f8aee6c5f1cfd4a681
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- j0Dv26UIG4xSXEKhYDh3AtgcZnaIxxD8+9pfdjVkH+RvCkpKvJTSOUM+jcY+RGA1EtwvGdszN6ln9f6xg17zDw==