FSNEXFusion
Historical archive
Fusion, archived
The original FSNEX, rebuilt. Every recovered Fusion block is searchable, from genesis on.
15,130,081 blocks · June 2019 to October 2025Open FSNEX (opens in a new tab)
Use case 03 · Historical blockchain archives
Archive a discontinued blockchain
When a chain's infrastructure goes away, people still need to look up their old transactions. BlockGaze turns a surviving node or backup into a searchable archive, as FSNEX does for Fusion.
A useful life beyond the last block
A chain's records stay useful after its last block. Former users need proof of what they held and sent, for tax records and other evidence, and researchers and communities want to study how the network was used. An archive explorer keeps transactions, token transfers and contracts open to all of them.
It starts with a data source
We need a running node, a backup of one, or other chain data that can still be read. We check what it holds before we agree on the scope.
How Fusion's history was recovered
After Fusion's public infrastructure went offline, FSNEX was rebuilt from a backup of a community member's node chain data. FSNEX indexes it from a node with no internet access, and all 15,130,081 recovered blocks are searchable, from genesis to the final recovered block.
Hosted by us or by you
BlockGaze can operate the archive, or it can run on your own infrastructure. A discontinued chain no longer grows, so its storage need does not grow over time either.
What we need from you
- A surviving node, a usable backup or recoverable chain data
- The network's rules and any custom transaction or token types
- The name and colour palette the archive should carry
- Where it should run: hosted by BlockGaze or on your infrastructure
See it for yourself
Try it on the Fusion archive
The same software your archive would run, serving Fusion's recovered history.
Before we talk
What communities and former chain teams ask first
What if only part of the history survives?
If blocks are missing from every copy, they stay missing. The explorer says where its data starts and ends.
Who hosts the archive?
BlockGaze can host it, or it can run on your own infrastructure. Hosting and operational responsibilities are agreed before deployment.
Can the archive keep the chain's own name and look?
Yes. The explorer supports a chain-specific identity, including its name and colour palette. FSNEX kept its own name when it was rebuilt with BlockGaze.
Can researchers use the data directly?
Yes. A read-only API makes the archive's indexed records available beyond the explorer. Read the API docs (opens in a new tab)
Your network, next
Let's take a look
at your chain
Launching a network, replacing an explorer, or preserving a piece of blockchain history? Tell us what you have in mind.
Discuss your network
A chain name, its current status and what you need are enough to start.
Prefer a direct message? X (opens in a new tab) · LinkedIn (opens in a new tab)