What Are Ethereum Transactions?

5 min read

Ethereum transactions are cryptographically signed data messages containing instructions that facilitate interactions on the blockchain. These interactions can range from transferring Ether between accounts to executing smart contract functions. This guide delves into Ethereum transactions, their architecture, and how to programmatically retrieve transaction data.

Overview

Transactions on Ethereum are fundamental to its operation, enabling decentralized interactions. They consist of structured data that instructs the network to perform specific actions, such as value transfers or smart contract executions.

Key Topics Covered

• Fundamentals of Ethereum transactions
• Transaction structure and types
• Programmatic access to transaction data

Transaction Fundamentals

A standard Ethereum transaction includes the following parameters:

• Nonce: A sequence number to prevent replay attacks.
• Gas Price: Fee paid per unit of gas (pre-EIP-1559).
• Gas Limit: Maximum gas allocated for the transaction.
• Recipient Address (to): Destination of the transaction.
• Value (value): Amount of Ether to send (in Wei).
• Data (data): Optional field for contract calls or messages.
• Signature (v, r, s): Cryptographic proof of the sender’s authorization.

👉 Learn more about gas fees

Ethereum Accounts

Ethereum features two account types:

1. Externally Owned Accounts (EOA)

   • Controlled by private keys.
   • Used for sending transactions.
   • Cannot store code or complex data.

2. Smart Contract Accounts

   • Deployed on the blockchain.
   • Contain executable code and storage.
   • Interact via transactions or calls.

Types of Transactions

1. Message Calls

   • Transfers Ether or interacts with smart contracts.
   • Example: Swapping tokens on Uniswap.

2. Contract Creation

   • Deploys new smart contracts.
   • Example: Uploading a decentralized app (DApp).

Transaction States

• Pending: Awaiting network confirmation.
• Queued: Held due to nonce sequencing.
• Cancelled/Replaced: Overridden by a newer transaction.
• Failed: Reverted due to errors or insufficient gas.

👉 Troubleshoot pending transactions

Transaction Architecture

Modern Ethereum transactions follow EIP-1559, which introduces:

• Base Fee: Dynamically adjusted by the network.
• Priority Fee (maxPriorityFeePerGas): Miner tip.
• Max Fee (maxFeePerGas): Upper limit for total cost.

Example Transaction Object:

{
  "from": "0x...",
  "to": "0x...",
  "value": "0x...",
  "data": "0x...",
  "nonce": "0x...",
  "gasLimit": "0x...",
  "maxFeePerGas": "0x...",
  "maxPriorityFeePerGas": "0x..."
}

Retrieving Transaction Data Programmatically

Use an Ethereum RPC endpoint (e.g., QuickNode) to fetch transactions:

curl -X POST https://YOUR-ENDPOINT \
  -H "Content-Type: application/json" \
  --data '{"method":"eth_getTransactionByHash","params":["0x..."],"id":1,"jsonrpc":"2.0"}'

Output Fields:

• hash: Transaction ID.
• blockHash: Block containing the transaction.
• value: Transferred Ether.
• gasUsed: Actual gas consumed.

FAQ

1. What causes a transaction to fail?

• Insufficient gas.
• Reverted smart contract logic.
• Incorrect nonce.

2. How do I speed up a pending transaction?

• Resubmit with a higher maxPriorityFeePerGas.

3. What’s the difference between gasLimit and gasUsed?

• gasLimit: Maximum units allocated.
• gasUsed: Actual units consumed.

4. Can I cancel a transaction?

• Yes, by submitting a replacement with the same nonce and higher fee.

Conclusion

Ethereum transactions power everything from simple transfers to complex DApp interactions. Understanding their structure and lifecycle is essential for developers and users alike.

Further Reading:

• Ethereum Whitepaper
• QuickNode API Docs

Got questions? Join our Discord or tweet us @QuickNode!

Feedback? Let us know how we can improve!