What is FusionScan?
FusionScan is a block explorer for PulseChain at scan.pulsefusion.io. Like PulseScan, it lets you look up blocks, transactions, addresses and tokens without a wallet. Unlike PulseScan and Otterscan, which run under pulsechain.com, it is a third-party service that indexes the chain with its own backend. According to the developer’s beta announcement on X, the backend is written in Go and stores the data in ClickHouse, a database built for fast analytical queries.
FusionScan does not say who runs it. Its domain, pulsefusion.io, also hosts the subgraphs that the auction pages of the Icosa app query; those subgraphs were offline (Cloudflare error 523) on 19 and 31 October. Hedron and Icosa were built by a pseudonymous team that publishes as PulseFusion (see listing criteria). Whether the same team runs FusionScan is not stated.
What works in the beta?
- Browsing blocks, transactions, addresses and tokens, including holder counts and the verified source and ABI of existing contracts such as HEX.
- An Etherscan-style API at
/api?module=…, meant to let scripts written for Etherscan work on PulseChain by changing the base address; the developer calls it mostly working. The calls we tried — block number, token supply, contract source and ABI — answered in Etherscan format on 31 October. - A Blockscout v2-style API at
/api/v2/…and a GraphQL API at/api/v1/graphql. - An MCP interface for AI agents is announced as mostly working; on 31 October its endpoint did not yet accept requests on the public address.
What did we check?
On 31 October 2026 we compared FusionScan with the official RPC rpc.pulsechain.com. The first three rows were read at block 27,940,458 (19:00 UTC), the transaction about three minutes later:
| Check | FusionScan | Official RPC |
|---|---|---|
| Latest block | 27,940,458 | 27,940,458 |
| Hash of that block (via GraphQL) | 0x12fea6db… |
0x12fea6db… |
| HEX total supply (Etherscan-style API) | 53,248,552,888.46675656 HEX | 53,248,552,888.46675656 HEX |
Block of transaction 0x58306d7b… |
27,940,475 | 27,940,475 |
A few matching numbers show that the indexer was in sync at that moment; they are not an audit. The supply figure in the token-page API (/api/v2/tokens/…) is refreshed less often and was behind the RPC on 31 October — for an exact figure, ask the RPC. For anything that moves money — contract source, owners, approvals — check on PulseScan or directly through the RPC as well (how).
What is still missing?
The developer lists internal transactions, NFTs, balance history and verifying new contracts as unfinished, plans a new interface next and is considering tracking of the Ethereum–PulseChain bridge. Until then, an empty list of internal transactions on FusionScan does not mean that a contract sent nothing — look the transaction up on PulseScan or Otterscan.
Reading the explorer needs no wallet. To call a contract, use its official app or PulseScan’s Write contract tab, not a beta tool (where to use tokens). FusionScan is listed in the Explorers section of community services.