# Compare Quantus local sync height with the network

A progressing network does not establish that your local node is synchronized. The explorer shows the network view; local node status or logs show your own progress. Both records must refer to the same mainnet.

- Canonical: https://iotahome.site/en/learn/quantus-local-node-vs-network-height
- Publisher: IOTA Watch
- Topics: Quantus
- Published: 2026-10-26
- Updated: 2026-10-26

## At a glance

A progressing network does not establish that your local node is synchronized. The explorer shows the network view; local node status or logs show your own progress. Both records must refer to the same mainnet.

## What to check

Record block height, hash and observation time on both sides, and verify mainnet rather than retired Planck. A shrinking gap suggests progress worth observing. Similar heights with different network identities require a configuration check before interpreting mining results. A network chart alone does not justify reinstalling a wallet.

## Example

Example: explorer height 1000 and local height 900 show a local gap at observation time. The missing 100 heights are not 100 personal rewards. Reconcile actual rewards separately using the reward address and its records.

## Continue

[Open project monitor](https://iotahome.site/en/projects/quantus)

## Sources and implementation

- [docs.quantus.com](https://docs.quantus.com/guides/mining/)
- [qtcscan.com](https://qtcscan.com/pools/)