BNB Chain is temporarily taking BscScan offline.
The primary block explorer for the network heads into scheduled maintenance starting at 14:00 on July 22. It will stay down for exactly three to four hours. During this window, developers and everyday users cannot access various BscScan web pages to track transactions.
API services are also halting.
This is a routine infrastructure adjustment. The core development team issued an official maintenance directive confirming the timeline. There is no underlying network hack or security threat driving the shutdown.
To keep operations running, the team explicitly directed users to utilize BSC_Trace as the primary alternative query channel. This fallback ensures uninterrupted access to on-chain data while the main explorer undergoes upgrades.
Developer Workflows Shift to BSC_Trace During Outage
A multi-hour API blackout forces an immediate technical pivot for decentralized application builders. Most dApp front-ends hardcode BscScan APIs to fetch user token balances and transaction histories.
When those endpoints go dark, any application lacking a secondary data source breaks.
This scheduled downtime highlights the operational risk of relying entirely on a single block explorer. By pushing traffic to BSC_Trace, the network operators are testing the load capacity of their secondary infrastructure. Developers who fail to route their API calls to the alternative explorer will face degraded performance until BscScan comes back online.