> For the complete documentation index, see [llms.txt](https://insightx.gitbook.io/atlas-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://insightx.gitbook.io/atlas-wiki/features/historical-mode.md).

# Historical Mode

## **Historical Mode**

*Explore how activity changed over time*

***

Historical mode lets you go back in time and see how wallet activity and connections looked at any moment.

Instead of relying on static snapshots, you can explore how a token evolved, tracking how wallets accumulated, moved funds, or changed over time.

<div align="center"><figure><img src="https://2669852347-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIm5UrU4W0fBxefosNB5y%2Fuploads%2Fg8FCkb111WaO4mq5Rtye%2Fgetsitecontrol__convert-video-to-gif__free.gif?alt=media&amp;token=d41192d6-38b0-427f-87ab-c5dee6ca8214" alt=""><figcaption></figcaption></figure></div>

***

### **What historical mode shows**

Historical mode lets you explore how activity on the map has changed over time, rather than only looking at the current state.

You can view the map at any point in time to see how wallet connections formed, how tokens were distributed, and how activity evolved. This makes it easier to understand when wallets were funded, how clusters developed, and how relationships between wallets changed.

Instead of relying on a single snapshot, historical mode gives you full context, helping you see the bigger picture and understand how the current state came to be.

### **Next steps**

Use [**Proxy Nodes**](/atlas-wiki/features/proxy-nodes.md) to uncover hidden relationships\
Check [**Behavioral Tags**](/atlas-wiki/features/behavioral-nodes.md) to understand wallet behavior


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://insightx.gitbook.io/atlas-wiki/features/historical-mode.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.