> For the complete documentation index, see [llms.txt](https://docs.solscan.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solscan.io/transaction-details/account.md).

# Account

#### 1. Overview

Display account's general information including:

* SOL Balance
* SPL Balance with a specific amount of each token.

<table><thead><tr><th width="150" align="center">Category</th><th align="center">Display Meaning</th></tr></thead><tbody><tr><td align="center">SOL Balance</td><td align="center">The total amount of SOL the account is holding and its value.</td></tr><tr><td align="center">SPL Balance</td><td align="center">The total amount of SPL token types the account is holding and their value.</td></tr><tr><td align="center">SPL Token Drop-down</td><td align="center">Details about specific SPL Tokens held by the account: Name, total amount, value.</td></tr></tbody></table>

#### 2. Transactions

Display real-time data illustrating transaction details. Users can track their transactions in the #Solana ecosystem, including: Transaction Signature, Block, Time of Transaction, Transaction Instructions, Transaction Maker and Transaction Fee.

<table><thead><tr><th width="150" align="center">Category</th><th align="center">Display Meaning</th></tr></thead><tbody><tr><td align="center">Signature</td><td align="center">The signature of the transaction.</td></tr><tr><td align="center">Block</td><td align="center">The block contains the transaction.</td></tr><tr><td align="center">Time</td><td align="center">Real-time update of the transactions from account.</td></tr><tr><td align="center">Instructions</td><td align="center">The transaction type.</td></tr><tr><td align="center">By</td><td align="center">Indicates the account making the transaction.</td></tr><tr><td align="center">Fee</td><td align="center">The amount of fees deducted from the action.</td></tr></tbody></table>

#### 3. SOL transfer

"Display real-time data regarding SOL transfer activities of the account. The areas available for users to track include:

* Transaction signature
* Block
* Time of transaction
* Transaction sender and receiver
* Changes in the SOL amount"

<table><thead><tr><th width="150" align="center">Category</th><th align="center">Display Meaning</th></tr></thead><tbody><tr><td align="center">Signature</td><td align="center">The signature of the transaction.</td></tr><tr><td align="center">Block</td><td align="center">The block contains the transaction.</td></tr><tr><td align="center">Time</td><td align="center">Real-time update of the transactions from account.</td></tr><tr><td align="center">From</td><td align="center">The sending account.</td></tr><tr><td align="center">To</td><td align="center">The receiving account.</td></tr><tr><td align="center">Change Amount (SOL)</td><td align="center">The amount of SOL increase/ decrease after the transaction.</td></tr></tbody></table>


---

# 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.solscan.io/transaction-details/account.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.
