# Transaction

**Type:** GraphQL objects

**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, Not Null): The original signed transaction command submitted to the network.
Includes metadata, payload, signers, and network information.
  - meta (TransactionMeta): Transaction-level metadata, such as gas price, gas limit, chain ID,
time-to-live (TTL), and creation time.
This controls how and when the transaction is processed by the chain.
  - networkId (String): The network identifier where the transaction is intended to run.
Example: `"mainnet01"` or `"testnet04"`.
  - nonce (String): A user-specified nonce string that ensures transaction uniqueness.
Typically includes random or timestamp data to prevent replay.
  - payload (TransactionPayload): The payload of the transaction, which defines the Pact code to execute
or the continuation to resume. This is the core logic being invoked.
  - signers (Signer): The list of signers required to authorize the transaction.
Each signer specifies a public key and associated capabilities
that define what actions they are permitted to authorize.
- 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, Not Null): 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, Not Null): 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.
  - sig (String)