Interpretation of the question: how many instructions are executed to perform an operation.
If correct:
C# is compiled to MSIL. You can inspect the generated MSIL using ILSpy. This can give a rough indication.
Generated MSIL is however not executed directly but passed to the JIT that converts the MSIL to instruction understood by the ALU. I don't know if there is way to see the instructions after the JIT. Never had the need for it.
Other option is to use NGEN on the assembly. NGEN creates a binary with native instructions for the target platform. You can use a disassembler on the output.
But my guess is that the curiosity is there from a performance perspective.
Influencing the JIT on codegeneration is not trivial (if doable).
Use a profiler to find the bottleneck and alter the C# code to improve performance is the most trivial and maintainanble way imho.
If there is no way to get the needed performance try to recode the needed parts in C(++).
C# is a high-level language and the level of abstraction adds some level of overhead. The JIT is however quite smart, outperforming it with handcrafted code is a challenge.