why1 reason
spend_windowspend_window_exceeded
this would take GDBO3HXSQCTGUW4SL6HC6ASMW4ZTSHMLNN4FYV62A4MBJEGT4TXWPCSK to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- f5fec1c11c2b225766f61bddfb6e1b23a9016869863195357a15852231c1baa6
- request
- d060abf3618a00c6ca10b1c18aaa80e5e6ae3a72cb2369fa11b6b4c9d29d7ea3
- transaction
- ab9608b45774642ad731c002739bff2354a84273e13a4e7c1312bda5aa48f0e2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72658
the chainentry 72658
- sealed to the entry before
- b359368e62b8a775e30c1bfe4db90a88fbf49e5c21f4affdb55f13cc1dcb4324
- this leaf
- 5aacdefa4b6ad0cac4a2714faa79f3a674efd81aa0881f51d0ada3f7ce3fb2b7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VKIUMkNuZw/eL+Y3PbJDXSw+Vg1SdeDPRfsZVW8cy5b4h9D/Eg+qkjIvjyKbFXXW/18koqojEj3PQ8olNJHYCQ==