why1 reason
spend_windowspend_window_exceeded
this would take GB7X6JQC5NKQJTXYX2RKE3N6LV2KBFGC2Y4FYOHAB6HGFUWI3VB5SNEC to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- d91c401e6aa292ec8efaf14ad17b64fc9e256b8e01dceea682336a70b124399e
- request
- 77b68d70bcaeb9a7df2b2aff53075ae1ba42b4ecc0a526964dfadfb4da7ba5db
- transaction
- 0dd9c88b09533985603f3c94c49a26b1cfc836525398a7d084e6527f3fe54c74computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6512
the chainentry 6512
- sealed to the entry before
- 8c85ba514e883b1e699a383f0aad2820f86bf9a0dd25d07b60e27ddd3f26aec5
- this leaf
- 75409fbad01adbea625a2a0686313cdea27d2437bd7686134d1320447e02d05b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- uxMXbDJaetoKwmSE/L6GSURjAIfh7+H8efsTB7iSr2neiBxB2CgYXF0DZUJXYOktrHlyKXRGVvWjAZwxPAYxAQ==