Aptoscan’s homepage says the site and its services will be sunset at the end of October 31, 2026, and asks users to export needed data beforehand. If you rely on its account history or saved transaction links, preserve both the records and the context of the export now. The notice concerns this explorer service; it is not a notice that the Aptos blockchain is shutting down.
Save the scope with the CSV
The homepage notice uses end of day without specifying a timezone in the displayed message. Do not invent a precise UTC cutoff from that wording. Plan around completing your archive before the final day, rather than relying on an assumed last hour. A bookmark to the service is not an offline copy of the record behind it.
Etherscan’s official Aptoscan export guide, published May 13, 2025, locates Export CSV on an account’s Transactions and Transfers tabs. It describes selecting filters and downloading the file. That is the published workflow, not a claim that an export was tested for your account. If the interface or a download is unavailable, preserve what you can access and identify the missing range separately.
| Archive item | Context to keep beside it | Check before relying on it |
|---|---|---|
| Transactions CSV | Account, network, tab and selected filters | Does the included period match the intended activity? |
| Transfers CSV | Account, asset filters and export time | Are multiple transfer rows being confused with separate transactions? |
| Important transaction records | Hash or ledger version, status and source URL | Can the identifier be checked independently of the old bookmark? |
| Order or exchange evidence | Order reference and the corresponding chain transaction | Does a chain receipt actually reconcile with the service’s account record? |
| List of missing material | Unavailable period or failed download | Is an incomplete archive being labelled complete? |
A file that opens is not necessarily a complete history
Open the downloaded file and check its first and last relevant records against the requested period. Keep the original export unchanged and make a separate working copy for sorting or annotation. Record the row count and filters in a short note. This is a practical integrity check, not a promise that the explorer has captured every kind of activity or that the file alone meets accounting requirements.
An invented example shows the problem: a user exports the Transfers tab with one asset filter, then later treats the result as every operation on the account. The file may be valid while that description is wrong. Likewise, combining two exports without checking what each row represents can count the same underlying operation more than once. Preserve the tab and filter labels so a future reader can reconstruct what was requested.
- Confirm the account and network before requesting the export; separate mainnet records from testnet activity.
- Download the relevant Transactions and Transfers views using documented filters, and record the selected scope.
- Open the files, inspect coverage and retain transaction identifiers for records you may need to explain later.
- Keep original files, a working copy and an explicit list of gaps instead of silently treating missing rows as zero activity.
Another data source has its own retention limits
Aptos’s transaction API documentation describes retrieving committed transactions with a starting ledger version and page size. It also states that a pruned version returns HTTP 410. Consequently, switching to a different endpoint is not a guarantee that every old record is retained there. An endpoint’s unavailable historical version is not, by itself, proof that the original transaction never happened.
For an important missing record, carry the network and transaction identifier to an appropriate alternative source, rather than searching only the old page title. Keep a service receipt or order reference as a separate record where applicable. Explorer data can establish a chain event, while an exchange or application may still need to explain its own internal credit. One source does not replace the other’s evidence.
The closure does not create a reason to reveal wallet secrets
Archiving public transaction information does not require giving a migration site your seed phrase or private key. A demand to transfer funds merely to preserve an explorer record should be verified independently. Save the data you need without publishing a full account dossier unnecessarily; public transaction identifiers can become identifying when combined with private order records.
For future exchange records, read how an order works, confirm supported assets and networks and use simple swap only for an offered route. Keep the order reference with any resulting transaction. These KOT.CASH links do not promise replacement Aptoscan archives or recovery of an incomplete export.
FAQ
Does an Aptos mainnet explorer closure shut down Aptos itself?
The displayed notice concerns Aptoscan’s site and services. Preserve needed records without reading a service closure as a blockchain shutdown instruction.
Can Aptos explorer testnet records replace my mainnet history?
No: confirm the network attached to the account and transaction. Keep the network with the archive so a matching-looking identifier does not lead to the wrong environment.
Will an Aptos explorer API always restore every missing old record?
A data provider can have retention limits. Aptos documents a 410 response for pruned versions, so check historical coverage rather than assuming an endpoint contains everything.