Skip to main content

Largest Rectangle in Histogram – Learning the Monotonic Stack the Hard Way (LeetCode 84)

Problem Overview

The Largest Rectangle in Histogram problem is one of those classic questions that looks simple but exposes gaps in pattern recognition very quickly. You are given an array where each element represents the height of a bar in a histogram, and your task is to find the area of the largest rectangle that can be formed.

Initially, I had no intuition for this problem. I could brute-force it mentally, but nothing scalable came to mind. Only after revisiting monotonic stacks again did the solution start making sense.


Key Insight

Instead of trying to form rectangles explicitly, flip the thinking:

Assume each bar is the shortest bar in the rectangle.

Once you do that, the only thing you need to know is:

  • The nearest smaller bar on the left
  • The nearest smaller bar on the right

Between these two boundaries, the current bar can safely extend and form a rectangle. This transforms the problem into finding previous smaller and next smaller elements — a perfect use case for a monotonic stack.


Approach

  1. Compute the index of the nearest smaller element to the right for every bar.
  2. Compute the index of the nearest smaller element to the left for every bar.
  3. For each bar, calculate the area assuming it is the minimum height.

The width of the rectangle becomes:

(right_smaller[i] - left_smaller[i] - 1)

And the area:

height[i] * width

Python Implementation

class Solution:
    def largestRectangleArea(self, heights: List[int]) -> int:
        
        left_smaller = [-1] * len(heights)
        right_smaller = [len(heights)] * len(heights)
        stk = []
        
        # Nearest smaller to right
        for i in range(len(heights) - 1, -1, -1):
            while stk and heights[stk[-1]] >= heights[i]:
                stk.pop()
            if stk:
                right_smaller[i] = stk[-1]
            stk.append(i)

        stk.clear()
        
        # Nearest smaller to left
        for i in range(len(heights)):
            while stk and heights[stk[-1]] >= heights[i]:
                stk.pop()
            if stk:
                left_smaller[i] = stk[-1]
            stk.append(i)
        
        ans = 0
        for i in range(len(heights)):
            current = heights[i] * (right_smaller[i] - left_smaller[i] - 1)
            ans = max(ans, current)

        return ans

Why This Works

The stack always maintains indices of bars in increasing order of height. When a smaller bar appears, it naturally defines a boundary where the current bar can no longer expand.

This ensures:

  • Each element is pushed and popped only once
  • Overall time complexity remains O(n)

What This Problem Taught Me

This wasn’t about memorizing a pattern. It was about realizing that some problems require you to stop thinking locally and instead assume a global role for each element.

Monotonic stacks don’t click immediately — but once they do, a whole category of problems starts looking familiar:

  • Next Greater / Smaller Element
  • Stock Span
  • Maximal Rectangle

If you’re struggling with this problem, that’s normal. The intuition comes from repetition, not talent.


Source Code

Full implementation is available here:
https://github.com/RohitSingh-04/Python-Solutions/blob/main/LC84.py

Comments

Popular posts from this blog

LeetCode 88 Explained: Four Approaches, Mistakes, Fixes & the Final Optimal Python Solution

Evolving My Solution to “Merge Sorted Array” A practical, beginner-friendly walkthrough showing four versions of my code (from a naive approach to the optimal in-place two-pointer solution). Includes explanations, complexity and ready-to-paste code. Problem Summary You are given two sorted arrays: nums1 with size m + n (first m are valid) nums2 with size n Goal: Merge nums2 into nums1 in sorted order in-place . Version 1 — Beginner Approach (Extra List) I merged into a new list then copied back. Works, but not in-place and uses extra memory. class Solution: def merge(self, nums1, m, nums2, n): result = [] p1 = 0 p2 = 0 for _ in range(m+n): if p1 >= m: result.extend(nums2[p2:n]) break elif p2 >= n: result.extend(nums1[p1:m]) break elif nu...

Introducing CodeMad: Your Ultimate Universal IDE with Custom Shortcuts

Introducing CodeMad: Your Ultimate Multi-Language IDE with Custom Shortcuts Welcome to the world of CodeMad, your all-in-one Integrated Development Environment (IDE) that simplifies coding and boosts productivity. Developed in Python, CodeMad is designed to make your coding experience smoother and more efficient across a variety of programming languages, including C, C++, Java, Python, and HTML. Whether you're a beginner or an experienced programmer, CodeMad is your go-to tool. In this blog, we'll dive deep into the workings of CodeMad, highlighting its unique features and easy installation process. The Power of Shortcuts CodeMad's intuitive interface is built around a set of powerful keyboard shortcuts that make coding a breeze. Here are some of the key shortcuts you'll find in CodeMad: Copy (Ctrl+C) : Duplicate text with ease. Paste (Ctrl+V) : Quickly insert copied content into your code. Undo (Ctrl+Z) and Redo (Ctrl+Y) : Correct mistakes and s...

Product of Array Except Self in Python | Prefix & Suffix Explained (LeetCode 238)

Problem Overview The Product of Array Except Self is a classic problem that tests your understanding of array traversal and optimization. The task is simple to state but tricky to implement efficiently. Given an integer array nums , you need to return an array such that each element at index i is equal to the product of all the elements in nums except nums[i] . The challenge is that: Division is not allowed The solution must run in O(n) time Initial Thoughts At first glance, it feels natural to compute the total product of the array and divide it by the current element. However, this approach fails because division is forbidden and handling zeroes becomes messy. This pushed me to think differently — instead of excluding the current element, why not multiply everything around it? That’s where the prefix and suffix product pattern comes in. Key Insight: Prefix & Suffix Products For every index i : Prefix product → product of all elements to t...