> 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/tics-scan-user-guide.md).

# TICS Scan User Guide

TICS Scan is a blockchain explorer designed to make it easy for users to explore and interact with the Qubetics blockchain. 

It provides a user-friendly platform to access detailed information about transactions, tokens, blocks, and smart contracts. With TICS Scan, users can track real-time activity on the blockchain, verify contract details, and analyze data like token transfers and holder distributions. It also supports features like contract verification, enabling developers and users to confirm the authenticity and security of deployed smart contracts. By offering transparency and powerful tools, TICS Scan ensures that both developers and community members can navigate the blockchain with confidence and ease.<br>

{% hint style="info" %}
**Here is the link to the TICSScan tutorial video (Testnet):** \
<https://www.youtube.com/embed/IE2K2Bt8nbI?si=bV5VhSZXT6a3ZFgO>
{% 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://qubetics.gitbook.io/qubetics-docs/getting-started/tics-scan-user-guide.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.