# transactions

**Type:** GraphQL subscriptions

**Description:**
Subscribe to transactions as they are confirmed on the Kadena network.

This subscription streams newly confirmed transactions in real time, allowing clients to react immediately
to network activity without polling. It is typically used by explorers, indexers, monitoring tools,
and analytics platforms to track transaction flow and update UIs as new data arrives.

By default, the subscription delivers transactions that have reached the minimum required confirmation depth,
ensuring they are finalized and indexed before being emitted.

The `quantity` parameter controls how many of the most recent transactions are included in the initial payload
when the subscription starts (default: 20). After the initial batch, new transactions are pushed to the client
as they are confirmed.

## Arguments
- quantity (Int): The number of most recent confirmed transactions to include in the initial payload
when the subscription starts. Defaults to 20.

## Response
**Type:** Transaction
**Description:**
Represents a transaction executed on the Kadena blockchain.

A `Transaction` encapsulates the full structure and outcome of a blockchain transaction —
from the original signed command to the resulting execution details.
Each transaction is uniquely identified by its `hash` and includes the submitted command (`cmd`),
associated signatures (`sigs`), and the execution result (`result`).

This type is fundamental for querying and analyzing blockchain activity, tracking execution outcomes,
and verifying signed payloads.

### Fields
- id (ID): Globally unique identifier for this transaction node.
- cmd (TransactionCommand): The original signed transaction command submitted to the network.
Includes metadata, payload, signers, and network information.
- hash (String): The unique hash of the transaction.
This value is derived from the signed command and serves as the canonical identifier
for the transaction on-chain.
- result (TransactionInfo): The result of executing the transaction.
Includes information such as success/failure status, events, continuation data,
and any state changes triggered by execution.
- sigs (TransactionSignature): The list of signatures associated with the transaction.
Each signature proves authorization from a required signer and is used to validate
that the transaction was properly authorized before execution.