why1 reason
spend_windowspend_window_exceeded
this would take GD3D3JKJPU7JMUDQCKCHB7IMIWWCE34SJ3P5VRSKVJTARSMEAK4TGWTA to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 4cf405a3574bc87f5f7bf7057a78d53fdadb496965c898776253fcc193ecb960
- request
- bd3136000d721ef9031f20b9c97898b4388797df1fed2cf46d57e40fd4c127a3
- transaction
- eef71b1ce606af30bb6dbb87c4fea583625f78ccfc080ba8ec5436f0ae7e8b90computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8594
the chainentry 8594
- sealed to the entry before
- b5606ca2958f9c4e4273601e5a5f1772a5080d056cd1998bbbef564d4121cdd2
- this leaf
- 499207471fba4db78eccc36a4a4d464afab7e21757d9b511c500919df4191201
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oEd5e7As9cGiasXSkCHj60+QG8+zleEpccthFBHrhlPh7079tb6ajLjbRWtnkYkQxuocfAtMijYSx1Jqu30yCA==