Watch: Wild Scenes In Jaipur As MS Dhoni Storms Into The Field To Slam Umpire

The 25th match of this year’s IPL between Rajasthan Royals and Chennai Super Kings in Jaipur saw it all. There were impressive cameos, fine performance with the ball, world-class clash, thrilling finish as well as a major controversy.  Chasing a modest 152, MS Dhoni-led Chennai Super Kings were staring down the barrel in the powerplay itself. Shane Watson, Suresh Raina, Faf du Plessis and Kedar Jadhav had departed inside the first six overs to leave the Super Kings reeling at 24 for 4.

But just when it looked like the Super Kings were set to suffer their second defeat of the season, MS Dhoni and Ambati Rayudu brought the defending champions right back into the game. The two scored fighting fifties while adding 95 runs for the fifth wicket. Ben Stokes ended the stand when he had Rayudu for 57. Dhoni, nonetheless, remained till the last over when the Super Kings needed 18 runs from the final 6 balls.

Read More: Tom Latham To Lead New Zealand Against Australia

The over started in the best possible manner for the Super Kings with Ravindra Jadeja somehow managing to hit Ben Stokes for a six. The next two balls went for four runs before Stokes castled MS Dhoni. The drama unfolded soon when on the fourth delivery the main umpire signalled a no ball and then all of a sudden backed out. It led to wild scenes as the ever-calm Dhoni stormed onto the pitch to vent his anger. The Super Kings skipper was absolutely furious as the umpires and even Stokes walked up to him to calm him down.

Read More: IPL 2019: Stephen Fleming Opens Up On MS Dhoni-Incident In Jaipur

Mitchell Santner then kept his calm and hit a six on the final ball to pull off a spectacular win for his team.

Following the game,  MS Dhoni, who scored 58,  was charged for breaching IPL’s code of conduct. The Super Kings skipper, who registered his 100th win in the IPL as captain, admitted to the level 2 offence. He was fined 50% of his match-fees for the incident.

Here is that clip showing that incident:

https://twitter.com/PRINCE3758458/status/1116408603588603905