Rice drives in 3 runs as Yankees beat Red Sox 9-2 to earn a doubleheader split

Ben Rice's three-run performance in Saturday's nightcap is the kind of late-inning breakout that reshapes DFS leverage on a slate. The Yankees' five-run eighth inning — anchored by Rice's two-run single — turned what looked like a competitive game into a blowout, and that offensive explosion matters less for the final box than it does for understanding game flow and ownership positioning. Rice himself remains a lower-owned catch in most Yankees lineups, which means his spike round makes him a viable late-swap candidate when the optimizer flags correlated upside in the back half of the order.

What stands out for slate construction is the nature of the scoring: this wasn't a home run barrage, but a sequence-based rally that punished Boston's bullpen depth. In a doubleheader split scenario, fatigue and bullpen availability become real variables. The game total sits at 8 runs, and Saturday's run eruption in the nightcap suggests the Yankees' offense can cluster scoring in tight windows rather than scatter it across nine innings. That pattern — concentrated run production, fewer at-bats per run — favors stack construction over chalk chalk fade. Rice's spot in the order and his sudden offensive role make him a candidate worth monitoring for Sunday and beyond, particularly if the Yankees' lineup holds stable.

For users building against a slate with the mlb dfs optimizer, the takeaway is simpler: verify Rice's playing-time role over the next 48 hours. Doubleheader splits often reset bullpen usage and starter availability, which can shift game totals and pace. If Rice earns consistent ABs in the order and the Yankees carry forward that eighth-inning mentality, late-swap ownership will trend heavier. Re-check exposure and confirm before lock whether his salary has adjusted for the uptick in relevance.