> 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/transaction-details.md).

# Transaction Details

#### Transaction Details Overview

<figure><img src="/files/ZtM1oz965rGphhjkwaRV" alt=""><figcaption></figcaption></figure>

1. Signature: Transaction ID/hash
2. Block: Slot number of the block that contains the transaction.
3. Timestamp: Read more about the Solana Proof of History protocol here: <https://docs.solana.com/cluster/synchronization>
4. Result:&#x20;

   Success/Failure: The result of transaction&#x20;

   Finalized (Max confirmations): The statement that the transaction has already been validated by validator nodes.
5. Signer: Sender Address.
6. Fee: Gas fee for the transaction.
7. Main Actions: Transaction breakdown into one or multiple transfers.
8. [tx MAP](/transaction-details/transaction-details/tx-map.md): transaction flow visualizer.
9. Your Notes: You can add notes/reminders/labels for this transaction.

**Create Associated Account:**

Making transactions on Solana means that you have to create a Token Account for each type of token that you want to make a transaction on. In case that you do not establish a token account to store the said token, the protocol you use automatically creates a token (associated) account for you.

![](/files/lCihdlrjfjw9FdXRp2PD)

1. Authority: Owner Wallet Address
2. Associated Account: Token Account Created by the Program.
3. Token Address: Token Address used in the transaction.

## **Instruction Details**

Solana transactions are composed of instructions. Each instruction contains the program ID it invokes, program instruction, and a list of accounts that the transaction needs to write or read. Instruction Details show information of the interaction among instructions, programs and accounts under the hood. For general users, we recommend hiding these details for better experience.

For example:

The below instruction includes:

* Interaction with Magic Eden v2 program
* Instruction Data: hex or encoded data.
* Input Accounts: all accounts the transaction writes or reads through this instruction
* Inner instructions: another layer of instructions where interactions with system programs occur.&#x20;

<figure><img src="/files/R7CA8Ftr5YbrdVgPKnZp" alt=""><figcaption></figcaption></figure>

**Program log**

A log of the execution of programs, showing all events that occur through instructions.

For general users, we would recommend hiding the details of this section for simplier experience.

<figure><img src="/files/9k4tbgeB3Qs0Gt0IfX5O" alt=""><figcaption></figcaption></figure>


---

# 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:

```
GET https://docs.solscan.io/transaction-details/transaction-details.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.