Hazlewood wreaks havoc as Australia crush South Africa by 214 runs in Durban

The fifth morning at Kingsmead in Durban belonged to Josh Hazlewood. Sitting at my desk in Dhaka, I watched the scorecard unfold — South Africa chasing 420, and Hazlewood's spell of 6/49 arriving like a quiet declaration of intent. After posting 390 in the first innings, Australia declared at 314/6 in the second, effectively taking the match into their grasp. South Africa collapsed to 284 and then a mere 206 in the second innings, losing by a massive 214-run margin. But this match isn't just about Hazlewood's spell; Matt Renshaw's outstanding 190 and 82 are equally significant. For a top-order batter to score 272 runs in a single Test is statistically exceptional. From my experience at the Dhaka data desk, I can say such performances are rarely seen. Renshaw's 190 in the first innings gave the team a massive platform, while his 82 in the second came in the context of a declaration — showing mental maturity. But here's the question — based on this one match, can we call Renshaw a 'breakout star'? I don't believe so. One match doesn't establish a trend. My 43 years of cricket observation tells me that the real test for a player who performs exceptionally in one match is the next few. Renshaw needs to prove consistency over 2-3 more Tests. Hazlewood's case is different. His career average isn't the point; using seam and reverse swing on a deteriorating Day-5 pitch to take 6 wickets is a mark of class. In Durban's humid conditions, the ball swings, and when the pitch breaks up on Day 5, it's heaven for pacers. Hazlewood capitalized on that opportunity. One intriguing aspect is that Australia didn't enforce the follow-on. Despite a 106-run first-innings lead, they chose to bat again and declared at 314/6. This was tactically the right decision. According to the follow-on rule, a lead of over 200 runs is required to enforce it, but with only 106, that wasn't possible. So Australia batted and set a target of 420 — the safest path to victory. South Africa's failure isn't new. After such a defeat at home in Durban, questions will be raised about their batting depth. 284 and 206 — they failed to post big scores in both innings. This points to structural issues. However, I don't think it's fair to call South Africa 'in crisis' based on one match. They're in a transition period, and such a home defeat will certainly dent their confidence. The most crucial aspect is that this win proves Australia's 'away-adaptable' Test capability. Winning in South Africa isn't just about improving the points table; it strengthens their position in the World Test Championship race. But I keep emphasizing — predicting a series outcome based on one match is dangerous. The remaining matches are the real test. Sitting at my desk in Dhaka, analyzing this match, I realized something — the PPDA dashboard or advanced metrics don't always shout; they silently arrange the truth. Hazlewood's 6/49 spell is like that — not just in numbers, but in the story behind it. The Day-5 pitch, humid conditions, and South Africa's lack of patience — these three elements combined to create this destruction. Now the question is — is this win permanent for Australia? My answer is — the next matches will tell. Renshaw's batting consistency, Hazlewood's workload management, and South Africa's batting improvement — these are the three things to watch in the remaining matches of the series.