> For the complete documentation index, see [llms.txt](https://docs.pancakeswap.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pancakeswap.finance/chinese/huan-ying-lai-dao-pancakeswap/info.md).

# 信息站（信息页面）

## 信息页面

在此查看 PancakeSwap 的原生分析站点：<https://pancakeswap.finance/info>

<figure><img src="https://raw.githubusercontent.com/pancakeswap/pancake-document/en/.gitbook/assets/image.png" alt=""><figcaption></figcaption></figure>

所有核心指标数据均来源于 PCS 内部索引器（Indexer），而索引器又从合约被调用时触发的事件中收集数据。

对于 PancakeSwap 内部索引器中的日期维度，我们使用国际标准时间（UTC）进行每日统计。因此，当 Dashboard 上的横轴显示日期时，它表示的是国际标准时间（UTC）下的日期。<br>

## 核心指标

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXemXpjzW0IqGPjz6IISjhcIXzWWeeFyxXU7XLRumCxM6WQsr4IKMP_mwDhiMDGY9EUDtKZAKoeYsbYUXwRc2C2KBvoSRo_-tlxq09zOJ1ajIq00cXM6z_7-2RNv3rVWj_kBmLiY4Q?key=G7-HCtdmBA4wyp9ESrWifFqi" alt=""><figcaption></figcaption></figure>

**Volume（交易量）：** 我们监控每个交易对的每日数据以及每个代币的每日交易数据。每日交易量的计算方式为：将当日每个代币的交易量乘以其价格。

**Total Value Locked（总锁仓价值）：** 从内部索引器获取所有池子，并读取每个池子的 reserve\_usd 或 total\_value\_locked\_usd。

**Price（价格）：** 在 PCS 内部索引器中，我们利用多个基础池来计算与美元相关的价格。主要的池子是稳定币交易池，我们使用交易量最高的交易池作为基础池，并根据交易量权重计算稳定币的美元价格。此外，基础代币与该链稳定币的交易池也被视为基础池，用以提供美元价格。

*未被列入白名单的代币，或未与白名单代币配对的代币，将被排除在这些计算之外。*

<br>


---

# 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 by asking a question.

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

```
GET https://docs.pancakeswap.finance/chinese/huan-ying-lai-dao-pancakeswap/info.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 `automate deployments from our CI pipeline` 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.
