> For the complete documentation index, see [llms.txt](https://resources.defirisk.intotheblock.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resources.defirisk.intotheblock.com/axelar-interchain-tokens/tokens-leaderboard.md).
# Tokens Leaderboard
**Overview**
This indicator focuses on analyzing and ranking tokens facilitated by Axelar's ecosystem according to the number of transactions they have been involved in. This specific indicator highlights the most actively used tokens within this framework, providing insights based on the transaction count.
**How can I use it?**
Identifying the top tokens by transaction count offers insights into which assets are most popular and widely adopted among users of the Axelar network. High transaction counts typically indicate strong user interest and utility.
By highlighting the most actively used tokens, this indicator also sheds light on the success of interoperability efforts. It shows which tokens are benefiting most from cross-chain functionalities, providing evidence of the practical utility of blockchain interoperability.
Analyzing the top tokens by transaction count can reveal trends in user behavior, such as preferences for certain types of assets or shifts in interest towards specific blockchains.
---
# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://resources.defirisk.intotheblock.com/axelar-interchain-tokens/tokens-leaderboard.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
