# AI Block Explorer

Read the blockchain has never been so easy, just ask the Chef, he knows everything happening in the Kitchen.

Explore at: <https://explorer.kitchen-layer.com/>

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPVjrj9q1xrGsbASaUOWn%2Fuploads%2FUh2rhZRsYJzD3Ie8NUsV%2Fchrome_7yae55B6D7.mp4?alt=media&token=07f676a0-9285-443e-8c59-9a918e655ee2>" %}

The AI block explorer represents Kitchen Layer's vision for next-generation blockchain data accessibility, building upon Blockscout's robust foundation while introducing revolutionary AI-powered capabilities.

At its core is the Chef, an AI agent seamlessly integrated into the search bar, enabling natural language queries for blockchain analytics and research. This breakthrough in user interaction is made possible by Kitchen Layer's standardized native functions, comprehensive method labeling system, and structured event emissions, ensuring unprecedented accuracy in AI-generated responses.

Beyond AI integration, the block explorer reimagines traditional blockchain data visualization. By leveraging Kitchen Layer's native functions, complex on-chain data is automatically processed and presented through:

* Interactive data tables
* Dynamic charts
* Visual analytics
* Intuitive graph representations

This transformation moves blockchain exploration beyond raw transaction logs and technical readouts, making on-chain data accessible and meaningful to users of all technical backgrounds. Users can now understand protocol interactions, track asset movements, and analyze market trends without requiring deep technical expertise.


---

# 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://kitchen-layer.gitbook.io/kitchen-layer-docs/cook-book/block-explorer.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.