@volen some remarks in no particular order:
- Use a pano-head. Adjust your pano-head’s least-parallax-point. In this pano it is not well adjusted and leads to problems.
- Your overlap is far too high. Aim for 20% or so. Too much overlap causes bad stitching, it puts unnecessary load on your CPU, takes up unnecessary amounts of space on your memory card, hard drive and backup drives, it causes the whole process to take longer and require more RAM.
- Your archive contains 49 images at 140MB. I cut this down to 8 images at 23MB. https://i.imgur.com/t1namQ2.png
- Always set your camera to manual mode when shooting panoramas. These shots were taken in aperture-priority mode. In some cases programs can compensate for differences in exposure, but in this case, with a single row, where the center of the pano is darker than the edges, the software looks at the image on the left and sets its average exposure to fit well with the others, but the image on the left is different than the ones in the center - it is land + sky, while the ones in the center are sea + sky, so the result is that the land looks consistent throughough the panorama but you can see that the sky is not https://i.imgur.com/tEKm7v8.png
- Shoot raw.
- Sometimes you should correct the lens distortion before stitching. The stitching software may be able to correct lens distortion, and it could do that based either on a database of lens distortion correction parameters such as lensfun, or it could do it based on control points. In your case doing it based on control points leads to bad results because due to the nature of the scene there are only small areas where you can place them. You can’t put them on water or on the clouds as those change between frames. You can put them on the ground closest to the camera but that means that the optimizations will be calculated based on that area of the frame at the cost of the areas without any CPs, and in this panorama its actually the areas without any CPs where misalignment will be most noticeable - the horizon. https://i.imgur.com/GC9HZLI.jpg leads to https://i.imgur.com/ZcW6m6f.png
- The things you put control points on are the things which will align the best. In this case you want the horizon to align. You can’t tell whether the shrubs are misaligned, but you can straight away see when the horizon is wonky. You may be tempted to put CPs on the most distant clouds. In this example, actually putting the CPs on the clouds https://i.imgur.com/xvDW4gc.jpg makes the lens distortion model of those two frames match and everything looks fine https://i.imgur.com/34ERfPh.png The rock at the bottom of the frame paid the price, but you don’t notice that as easily as you do a badly stitched horizon. However, even though the horizon touches perfectly between frames, the overall pano is wonky because the CPs were on moving objects.
- In this pano I would put the CPs on the most distant non-moving parts of each frame https://i.imgur.com/fv6mr6p.jpg
- Closing remarks: adjust your equipment before shooting to avoid such situations. Taking 3 more minutes to double-check and plan while shooting can easily save you 2 hours after shooting. Try to visualize the parts of the scene where stitching errors will be most visible and the parts which will be most usable for placing CPs and plan your shot accordingly.
Best I could get:
at first lemme thank you for your time and effort 
