> For the complete documentation index, see [llms.txt](https://qubetics.gitbook.io/qubetics-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://qubetics.gitbook.io/qubetics-docs/getting-started/validator-application-user-guide/validators/active-validators-tab.md).

# Active Validators Tab

<figure><img src="https://2711441218-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F36u23gOZEZc21qS2BbPV%2Fuploads%2FBw0BKz1CJAWaVoOdPwMy%2Fimage.png?alt=media&amp;token=3d79ff9b-c515-414b-95cc-7ec78418c031" alt=""><figcaption></figcaption></figure>

### Validators Table

The Active Validators Tab serves as a centralized hub for understanding validator contributions and making informed staking decisions. Delegators can assess validator performance, reward structures, and operational status to choose validators that align with their goals. Validators can monitor their metrics to evaluate their standing within the network and optimize their operations for better performance.

* **Serial Number (Sr. No.)**\
  Each validator is assigned a unique serial number for quick reference and streamlined navigation. This allows users to locate and compare validators effortlessly within the table.
* **Name**\
  The Name column displays the unique names of validators, such as **"Shinobi Validator"** or **"Sherlock Nodes"**. This identifier helps delegators easily recognize and select validators for staking, making the interface user-friendly and intuitive.
* **Validator Address**\
  The Validator Address represents the unique blockchain address associated with each validator *(e.g., 0x47865...46845)*. Clicking on the address provides a more in-depth view of the validator’s metrics, performance history, and contribution to the network. This feature allows users to make informed decisions based on detailed validator data.
* **Status**\
  The Status column indicates the validator's operational state, ensuring transparency in their participation within the network. This status overview helps delegators identify reliable validators for staking:&#x20;
  * **Active:** The validator is currently contributing to block validation and participating in consensus.
  * **Deactivating:** The validator is in the process of exiting from active participation but may still be holding delegators' stakes temporarily.
  * **Inactive:** The validator is not currently validating blocks, potentially due to downtime or other operational reasons.
* **Total Stake**\
  The Total Stake column reflects the total number of tokens staked with each validator, including contributions from delegators and the validator themselves.&#x20;
* **Commission**\
  The Commission column displays the percentage of staking rewards retained by the validator as a fee for their services.&#x20;
* **Self Stake**\
  The Self Stake column highlights the amount of tokens the validator has personally staked to maintain their eligibility.&#x20;
* **Delegators**\
  The Delegators column shows the number of users who have staked their tokens with the validator *(e.g., 2)*.&#x20;


---

# 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://qubetics.gitbook.io/qubetics-docs/getting-started/validator-application-user-guide/validators/active-validators-tab.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.