Binance paused Bitcoin withdrawals as blockspace congestion intensified

Binance temporarily stopped Bitcoin withdrawals on May 7, 2023, saying the Bitcoin network was congested, then restored the service roughly 91 minutes later. The interruption mattered because it turned a network-wide competition for blockspace into an immediate custody constraint at the largest crypto trading venue by reported volume: customers could trade within Binance, but for the duration of the pause they could not move BTC from the exchange over Bitcoin’s base layer.

Binance’s public posts establish a tight chronology. The suspension post was issued at approximately 15:07 UTC and the resumption post at approximately 16:38 UTC, based on the timestamps encoded in the posts’ public identifiers. The company said its team was working on a fix and described funds as safe. It did not publish a technical incident report, affected-withdrawal count, wallet inventory or amount of BTC delayed in that first interruption.

Congestion was real; Binance’s response was its own

Bitcoin transactions first wait in a node’s memory pool before miners select them for blocks, generally favoring transactions that pay higher fees per unit of block weight. When demand exceeds the blockspace being produced, lower-fee transactions can remain unconfirmed while users seeking faster settlement bid more aggressively.

Contemporaneous reporting by Decrypt cited a mempool.space snapshot of about 395,000 unconfirmed transactions on the afternoon of May 7, compared with 56,500 on April 26 from Blockchain.com. Those figures came from different providers and point-in-time observations, so they show the scale and direction of the backlog rather than a perfectly comparable series. A mempool is also node-specific and changes continuously as transactions arrive, confirm, expire or are replaced.

The network backlog did not mechanically require every exchange to disable withdrawals. OKX posted during Binance’s interruption that its Bitcoin deposits and withdrawals remained operational, while warning that on-chain costs were high and suggesting its Lightning Network option. That contrast indicates that Binance’s pause reflected how the exchange had configured, funded and managed its own withdrawal queue under stressed fee conditions, not a shutdown of Bitcoin consensus or a universal inability to broadcast transactions.

Ordinals and BRC-20 intensified blockspace demand

The fee pressure coincided with rapid use of Ordinals inscriptions and the experimental BRC-20 format. Inscriptions place content in Bitcoin transactions, while BRC-20 used inscription data to deploy, mint and transfer fungible-token balances interpreted by off-chain indexers. These activities competed for the same finite base-layer blockspace as ordinary BTC transfers.

The timing supported a connection between inscription activity and congestion, but the event-day record did not prove that every pending transaction, or Binance’s specific backlog, came from BRC-20. Nor did the Bitcoin protocol distinguish an exchange withdrawal from an inscription when ordering transactions; miners saw valid transactions and their fee rates. The defensible conclusion is that a new source of demand was intensifying fee competition while Binance’s processing assumptions were tested.

What the pause showed

The May 7 interruption exposed the difference between Bitcoin’s network availability and access through a custodian. Bitcoin continued producing blocks, and users controlling their own keys could still broadcast transactions if they accepted prevailing fees and confirmation uncertainty. Binance customers depended on the exchange to construct, batch, fund and broadcast withdrawals from wallets it controlled.

That distinction was institutionally important after the failures of several centralized crypto firms in 2022, but the pause alone was not evidence of insolvency or missing customer assets. Binance said withdrawals resumed, and the first event lasted about an hour and a half. The surviving public record does not independently prove the status of every queued customer request at resumption.

No clean market-price reaction is assigned to the incident. Bitcoin traded continuously across venues, the withdrawal restriction was brief, and congestion and inscription activity were already visible before Binance’s announcement. Without a specified venue, event-study method and counterfactual, a contemporaneous price move could not be attributed to the pause alone. The verified May 7 development was operational: unusually heavy demand for Bitcoin blockspace was strong enough to interrupt base-layer withdrawals at a systemically important exchange, while the network itself continued settling transactions.