> For the complete documentation index, see [llms.txt](https://docs.catalyx.solutions/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/console-guide-canton/validators/balances-and-traffic.md).

# Balances & Traffic

{% hint style="info" %}
Both tabs are **read-only in 2.0**. There is no top-up, purchase, mint, or transfer action in the console in this release. Traffic purchases and Canton Coin transfers are performed through the Wallet UI or the Canton console.
{% endhint %}

## Balances

Canton Coin holdings, read from the network's Scan service.

### Metric cards

| Card               | Meaning                                                |
| ------------------ | ------------------------------------------------------ |
| **Total holdings** | The validator's total Canton Coin balance              |
| **Unlocked**       | The portion available to spend                         |
| **Locked**         | The portion locked in contracts. Amber when above zero |

### Snapshot

<table><thead><tr><th width="240">Row</th><th>Meaning</th></tr></thead><tbody><tr><td><strong>Owner party</strong></td><td>The party the balance belongs to.</td></tr><tr><td><strong>Available coin</strong></td><td>Spendable amount at the time of the snapshot.</td></tr><tr><td><strong>Record time</strong></td><td>Ledger time the snapshot was taken.</td></tr><tr><td><strong>Migration ID</strong></td><td>The Canton migration this balance is recorded against.</td></tr><tr><td><strong>Computed as of round</strong></td><td>The mining round the figures were computed for.</td></tr></tbody></table>

### Holding Fees

**Total**, **Unlocked**, and **Locked** holding fees — the ongoing cost of holding Canton Coin.

All amounts are formatted to exactly two decimal places, with thousands separators. A missing value shows as `—`.

### States

| Situation                                  | What you see                                                                                                                 |
| ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
| Scan has no balance for this validator yet | **No balance returned** — *Scan endpoint reported no balance for this validator yet.* Normal for a newly onboarded validator |
| The request failed                         | **Failed to load balances**, with the error                                                                                  |

***

## Traffic

Synchronizer traffic counters, read from the participant.

Canton meters the data a participant sends through the synchronizer. Each participant gets a base allowance that refills over time, and can purchase extra traffic beyond it. This tab shows where the validator stands against both.

### Metric cards

All three are byte-formatted (`B`, `KB`, `MB`, `GB`).

| Card               | Meaning                           |
| ------------------ | --------------------------------- |
| **Extra consumed** | Purchased traffic consumed so far |
| **Extra limit**    | Total purchased traffic allowance |
| **Base remaining** | Remaining base allowance          |

{% hint style="warning" %}
When **Base remaining** is near zero and **Extra consumed** is approaching **Extra limit**, the participant is close to being throttled by the synchronizer, and command submission will start failing. Purchase additional traffic through the Wallet UI before that happens.
{% endhint %}

### Routing

**Domain ID**, **Participant ID**, and **Endpoint**, each with a copy button. Shown when the synchronizer reports them.

### Counters

**Last consumed cost**, plus any additional counters the synchronizer returns, with humanised labels. The set of counters depends on the Canton protocol version, so this section is deliberately open-ended.

### States

| Situation          | What you see                                                            |
| ------------------ | ----------------------------------------------------------------------- |
| Loading            | *Loading traffic status…*                                               |
| No counters yet    | **No traffic data** — *The synchronizer has not reported counters yet.* |
| The request failed | **Failed to load traffic**, with the error                              |


---

# 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.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/console-guide-canton/validators/balances-and-traffic.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.