> For the complete documentation index, see [llms.txt](https://docs.fyuz.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fyuz.fun/trader-tools/wallet-explorer-and-top-traders.md).

# 🕵️ Wallet explorer & top traders

## 🏆 Top traders (per token)

Every token page has a **Top Traders** tab: the PnL leaderboard for that specific token, with labels for notable wallets (creator, whales 🐋). See who's actually making money on the token you're about to buy — and whether they're still holding.

## 🔍 Wallet explorer

Every address across Fyuz links to a full wallet profile:

* complete trade history,
* realized + unrealized PnL and win rate,
* tokens traded and total volume.

Found a wallet that's consistently early? Its whole track record is one click away.

{% hint style="info" %}
👁️ There are no private books on a public chain — the explorer just makes the data readable. Your wallet is equally visible to everyone else.
{% endhint %}


---

# 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://docs.fyuz.fun/trader-tools/wallet-explorer-and-top-traders.md?ask=<question>&goal=<endgoal>
```

`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.