> For the complete documentation index, see [llms.txt](https://faq.get-protocol.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faq.get-protocol.io/get-protocol-tokenomics/viewing-usdget-on-chain.md).

# Viewing $GET  On-Chain

## Viewing $GET fuel per ticket & event through the Community Dashboard

The GET Protocol community have created a dashboard for viewing the $GET usage of tickets as they flow through the protocol:

Brom's Community Dashboard:

{% embed url="<https://dashboard.get-community.com/>" %}

0xMartijn's Dashboard:

{% embed url="<https://dune.com/0xmartijnb/get-protocol-nft-tickets>" %}

## Viewing $GET on-chain via GET Protocol's SubGraph

Using our subgraph anyone can get a clear picture of [$GET](https://twitter.com/search?q=%24GET\&src=cashtag_click) flowing through the protocol, fuelling event tickets globally. The queries allow for a breakdown across event metadata and usage data, aggregated by all-time & per-day.

**You can access the subgraph below:**

{% embed url="<https://thegraph.com/hosted-service/subgraph/getprotocol/get-protocol-subgraph>" %}

You can also read more about the functionalities available with GET Protocol's SubGraph in our 'Mainnet' story hub article:

{% embed url="<https://www.get-protocol.io/content/mainnet>" %}


---

# 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://faq.get-protocol.io/get-protocol-tokenomics/viewing-usdget-on-chain.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.