Am I raising the bar or slowing everyone down?

Your reviews are thorough, people wait on them, and somewhere along the way you lost the ability to tell whether you are raising the bar or just being the bottleneck. When your work becomes a gate everyone stands at, that doubt is honest and worth listening to. It does not mean your standards are wrong. Thoroughness has a point of diminishing returns. The first pass catches the things that matter, and every real find protects the codebase. But past a certain depth you may be polishing what is already good enough while people wait, ship late, and quietly route around you. The skill now is knowing when a review is done. Try sorting your comments into two piles: must-fix and nice-to-have. Send the must-fix as blockers and the rest as optional notes. Give yourself a rough time budget per review. You keep the rigor where it protects the work, and you stop being the wall the whole team leans against.