why1 reason
spend_windowspend_window_exceeded
this would take GBH5HMVOUAL62ZHBFIHKPP3GTAGDYCLMDCRZ6EYBBHHMY7NMLSTBRPMQ to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- ea8ec41a6f1a7867368d8cd71bf66ae3416cfe5ad444b079d8cd6a8f2d36c67a
- request
- 7fab328d4d0d44917228dcd0ba438481df862f990ba727d33003eb0b9a83fc4c
- transaction
- ec7ac76f1c35f89726c4d4824aff5323f54486b198b80d48a947f9aa20b32b1acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22279
the chainentry 22279
- sealed to the entry before
- 94827fd131092ffebcdfb9703d00a409f6e478c363e7195c749000c43863cc4f
- this leaf
- 5b574cc00cb3153f47c73ff0454432dce8c292effed18dfca73300e1faea2d43
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zdD5LrgLHPwyObO7Yc5WgWUtkLKhTexVDW8rj28a6ZMuTlggsNZDpCN5/ERaMrmVANKeJSvvRf7ps+GJZutaDQ==