why1 reason
spend_windowspend_window_exceeded
this would take GB2JVTYTQUPCXH6MVOA5OWCRNMKHNNQL2XJNEKLUPGOT4LAWELPXZTKP to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- ac9b23824ee5f100730cf836f412a4abaa4be2ab23d4c9ca5d67e785499fce1e
- request
- ae897c96b1f423f8b571268568995a92ed938f0c31009bce2b81a5efa18b4e06
- transaction
- bc51c8d2b02cb9ef37352cd9da6e62b0c15a63bc69389b55a6804feb960061d2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8064
the chainentry 8064
- sealed to the entry before
- 33aa1880df68582e3ecae97c81a375f79e0ff6d1a312911b31f109567dcb4446
- this leaf
- 2be75ebb8e110ceb23ac7c4e3327a43972a0419027294f31a720108af7bec393
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yqKm3GrSn8joAacB1rQuhHb4QJUXyYQMcf2qQy4ZRD6GcsWXt9bMNX4NDAOmlDWfoIAZBlBujEs2vq6aFi3gAw==