Events Leading to the Crash of Mantra's OM Token Revealed by Glassnode

Blockchain surveillance platform Glassnode has revealed events that occurred on-chain

Blockchain surveillance platform Glassnode has revealed events that occurred on-chain, leading to the crash of Mantra’s OM token.

In a recent commentary, blockchain analytics platform Glassnode presented important information around the dramatic collapse of Mantra’s OM token, which nosedived 98% on April 13, 2025, in under an hour.

While the crash has already triggered massive losses for investors, Glassnode’s latest report highlights what happened behind the scenes using behavioral metrics such as exchange flows, holder concentration, realized capitalization, and user activity.

Price Collapse and Exchange Behavior

According to Glassnode’s data, OM’s price dropped sharply below the $1 mark within a few hours, leading to panic across the market. However, despite this rapid decline, there were no major token inflows to centralized exchanges in the 10-minute time frame ahead of the crash.

"Looking at exchange flows (10-minute resolution), we see no major inflows before the collapse. The largest spike comes after the crash – ~38M $OM at $0.71 on April 14, 08:20 UTC – suggesting reactionary moves, likely retail panic or opportunistic trading."

Interestingly, the platform found no major token inflows to centralized exchanges before the collapse, suggesting that the initial crash was not preceded by whales or insiders trying to offload positions en masse.

"This pattern strongly indicates a reactionary wave of panic selling, likely from retail investors or opportunistic traders seeking to unload or trade during the volatility."

On the other hand, exchange outflows surged shortly after OM hit its bottom. Glassnode interprets this behavior as potentially resulting from users withdrawing tokens post-liquidation, taking advantage of cheap buys, or exchanges minimizing exposure due to liquidity risk.

Shifting Holder Concentration and Realized Cap Movements

Before the crash, the percentage of OM supply held by the top 1% dropped modestly, from around 96.4% to 95.6%. Glassnode stressed that while this dip isn’t record-breaking, it is significant, given the token’s extremely concentrated supply structure.

"This metric excludes known team, contract, and centralized exchange wallets, implying that either large non-team holders recirculated their tokens or that liquidation events forcibly dispersed holdings."

This slight reduction in concentration might reflect growing unease among big players or signals of internal rebalancing, but it wasn’t enough to trigger early red flags, making the crash more difficult to anticipate.

Further, OM’s realized capitalization, a measure of the aggregate cost basis of all holders, plummeled by $740 million (20%) between April 13, 18:30 UTC and April 14, 03:10 UTC. This kind of value loss, especially within a short window, shows signs of large-scale liquidations or forced selling.

Notably, the sharp reset of the cost basis suggests that holders were exiting at losses en masse, confirming that the event was not just a typical correction.

Network Activity Spikes and LTH Movements

Meanwhile, Glassnode confirmed that a massive increase in on-chain activity accompanied the price collapse. Transfers of OM tokens skyrocketed, hitting a peak of 1,400 transactions within 10 minutes. Before this, activity had remained relatively flat, and it tapered off shortly after the peak.

Similarly, the number of active addresses surged during the crash, topping out at 574. This indicates that the panic was not limited to a handful of addresses but rather a broad set of participants across the network. Such a widespread reaction points to the idea of a systemic shock rather than a coordinated dump by a few wallets.

This rise in transfer count was mirrored in $OM's active address count, indicating a broader participation, peaking at 574 active addresses. These figures suggest that the #MantraOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOmOm