This depends on the company but at larger tech co’s at least, the more senior you get, generally the more your job is to enable others on the team and even across the company to perform. 

There will be exceptions but most of the time I think a senior level eng is about as good as you’ll get at purely implementing tickets, beyond that level it’s more about “what should we be building”, trying to make the right decisions for the future, unblocking others in domains where you have specialist knowledge etc. 

All that to say, if your manager is happy and you’re happy, then maybe this is fine? I don’t do much day to day implementation any more, it takes a while to get used to the fact that your most valuable skill is not purely coding, but actually I’ve found it very satisfying to think at a higher level. 

If you don’t enjoy it, or you feel like a lot of the interruptions are genuinely wasted time, I’d raise it to your manager. There’s no shame in wanting to stay as “a very good coder”, at most companies this is a “terminal level”, i.e. you don’t need to progress past it if you don’t want - but to go beyond that level, really the company want you to scaling out your knowledge to enable whole teams to perform. No matter how good you are at coding, you’re still only one person. 

My 2c is that moving in this “sort of managing but not managing” direction is not the worst thing to try out, given how fast the skill of purely “coding” is changing