According to on-chain analysts, LTHs “broke their silence” and began aggressive distribution . In the first few days of June alone, these holders offloaded roughly $2.4 billion worth of Bitcoin
. The selling came from a broad cohort, but the most striking signal arrived from the deepest vaults: 165 long-dormant wallets that had been idle for years moved approximately 5,073 BTC during May, with one address dormant since August 2010 waking up on May 31
. The trend extended into June, with a 2014-era wallet moving 109.86 BTC on June 1
.
This wasn’t just profit-taking. It was a psychological regime change—the strongest hands in the market, who had absorbed supply for months, were suddenly distributing into a weakening bid.
If LTH selling was the slow-burning fuse, the institutional unwind through U.S. spot Bitcoin ETFs was the accelerant. By June 2, the ETFs had posted 11 consecutive days of net outflows, a streak that began in late May . The two-day June tally alone topped $1 billion in outflows by June 3
.
The numbers quickly escalated into historic territory. At the peak of the panic, U.S. spot Bitcoin ETFs recorded a single-week outflow of $3.4 billion—the largest withdrawal event since the funds launched in January 2024 . The prior three weeks had already seen roughly $3.8 billion exit the complex over five straight losing weeks dating back to late January
.
BlackRock’s iShares Bitcoin Trust (IBIT), the bellwether of institutional Bitcoin demand, posted a near-record $527 million single-day outflow on May 28—its second-worst day ever, just shy of its all-time record . On June 2, IBIT shed another $440 million as the outflow streak hit 11 days
. Earlier in the run, IBIT saw $177.94 million exit on May 29, the ninth straight day of redemptions
.
Not every data point requested was available in the reporting. Precise percentage cuts by Jane Street and Goldman Sachs were not found in the sources, and the specific cumulative ETF outflow figure starting from May 15 was not isolated in the available data. What is clear is the sustained, accelerating pace of institutional selling that acted as a continuous weight on price.
The most violent chapter of the crash played out in the derivatives market. As Bitcoin breached critical support levels, a cascade of forced liquidations tore through overleveraged positions. On June 3—the peak of the carnage—nearly $1.84 billion in leveraged crypto positions were wiped out in a 24-hour window, the largest such event since February 5 .
The asymmetry was brutal. Of that $1.84 billion, over $1.66 billion were long positions, versus roughly $200 million in shorts—meaning approximately 90% of the liquidations hit bullish bets . Bitcoin longs alone absorbed $883.66 million of the damage, with Ether longs accounting for another $475.73 million
.
The liquidation cascade had, in fact, begun a day earlier. On June 2, a separate wave wiped out $727 million in leveraged long positions in a single day as Bitcoin plunged 5% below $68,000 . The market’s leverage had climbed to levels last seen before the October 2025 crash, leaving it acutely vulnerable to a cascading sell-off
.
Several triggers converged in the same narrow window to spark the sell-off:
A specific reading for a named “Bitcoin Volatility Index” was not available in the sourced reports.
What made this sell-off distinct was the breadth of selling pressure across every major market cohort—long-term holders, institutional ETF investors, and leveraged derivatives traders all heading for the exits at once.
The $61,300 low on June 4 represented a 13% three-session collapse , a 25%+ month-to-date decline
, and a 12% weekly drop
. It was Bitcoin’s lowest point since February 6, and the sell-off pushed the cryptocurrency to the floor of its entire 2026 consolidation range
.
Whether the move marks a capitulation bottom or the start of a deeper trend depends on whether long-term holders resume their accumulation pattern—and whether institutional capital returns to the spot ETFs that served as the primary demand engine throughout Bitcoin’s post-2024 rally.
Comments
0 comments