Insider breaks down potential Zach LaVine’s move to Lakers

Insider breaks down potential Zach LaVine’s move to Lakers

Photo: Chicago Bulls/Twitter

Recent reports swirling around the NBA suggest that the Chicago Bulls might be on the verge of trading Zach LaVine, with the Los Angeles Lakers emerging as a potential destination.

NBA insider Shams Charania provided valuable insights into a potential trade scenario. According to him, the Lakers would need to make significant roster moves to match LaVine’s substantial salary, emphasizing the importance of a third high-level scorer after the Lakers’ recent loss against the Kings.

“Last night I think is a good example of why having a third player than can score the ball at a high level,” Charania said on Run It Back, referring to the loss against the Kings. “I think D’Angelo Russell played well last night. He’s played well the last couple games, making threes. So he’s coming on as a scorer right now.

“But having a third guy, having a guy that can add more offensive punch, that’s why there’s a level of interest in LaVine from what I’m told.”

Charania shared his insights on the potential timing of a move, pointing out that mid-December could open up opportunities for the Lakers.

This timeframe aligns with the trade eligibility of key players, including D’Angelo Russell, Rui Hachimura, and Austin Reaves, who were re-signed in the summer.

However, Charania raised crucial questions for the Lakers, considering LaVine’s hefty contract. The star guard is in the second year of a five-year, $215 million deal, making him a significant financial commitment.

With limited trade assets, including just one first-round pick, the Lakers face strategic decisions on whether to pursue LaVine.

As the trade landscape evolves, the Lakers have the coming month to assess their team dynamics and answer pivotal questions surrounding potential moves for LaVine.



Check out our Latest News and Follow us at Facebook

Original Source

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *