# ENS

Chainlyze integrates seamlessly with Ethereum Name Service (ENS), enhancing the usability of our platform by allowing users to interact with blockchain addresses through human-readable names. This integration simplifies the process of identifying and analyzing wallet addresses by replacing or supplementing traditional hexadecimal addresses with more memorable and meaningful names.

<figure><img src="/files/8hEVmkkmJ5hS9tHD3xxl" alt=""><figcaption></figcaption></figure>

**How It Works**

* **Search Using ENS Names:** Users can input ENS names instead of the usual complex blockchain addresses when searching for wallets on Chainlyze. This feature makes it easier to navigate and understand blockchain transactions and balances.
* **Automatic ENS Recognition:** When a user connected to Chainlyze has an associated ENS name, it automatically appears within brackets next to their blockchain address throughout the platform. This enhances clarity and helps in recognizing and remembering user identities more easily.

**Utilizing ENS on Chainlyze**

1. **Enter ENS Name in Search:** Instead of typing a long blockchain address, simply use an ENS name like `example.eth` in the search field to access the associated wallet’s analytics.
2. **View Automatic ENS Displays:** For any wallet that includes an ENS name, Chainlyze will automatically display this name next to the corresponding blockchain address in all relevant sections of the platform.

This integration not only makes the user experience more intuitive but also leverages the power of ENS to foster a user-friendly environment for exploring blockchain data.

<br>


---

# Agent Instructions: 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 current page URL with the `ask` query parameter:

```
GET https://docs.chainlyze.ai/introduction/integrations/on-chain-integrations/ens.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.