🔮
Ethereum
  • General
    • What is Ethereum
      • Ethereum & Bitcoin General Comparison
      • Singleton State
      • The Ethereum Virtual Machine (EVM)
      • Opcodes (operation codes) EVM
      • Ethereum Client
      • Forks
      • Gas (wei)
        • EIP-1559
        • Table Conversion (wei)
      • Proof of Stake (PoS)
      • Proof of Authority (PoA)
      • The Beacon Chain
      • Networks
        • Ethereum mainnet
        • Goerli
      • Account-based model & UTXO-based model
      • Externally Owned Account (EOA)
      • Node Clients
        • Geth
        • Nethermind
      • Contract Account
      • Smart Contract Upgradeability
      • Ultrasound Money
      • Merkle Trees
        • Patricia Merkle Tree
      • Tries
        • State Trie
        • Storage Trie
        • Transactions Trie
        • Receipts Trie
      • Transactions
        • Ethereum Transaction Architecture
      • World State
        • Chain of States
        • Chain of Blocks
        • Stack of Transactions / Mempool
      • Contract Creation
      • Message Call Transaction
      • P2P Network
      • Web3.js
      • Ether.js
        • Smart Contract Interaction Example
      • Web3.js vs Ether.js
      • Node Providers
      • ENS (Ethereum Name Service)
      • Web3 dapp
      • Escrow
      • Multi-signature
      • ERC-20 tokens
        • Send ERC20s to Contracts
      • NFTs
        • ERC-721 and ERC-1155
      • Solidity
        • State Variables
        • Data Location
        • Numbers
        • Modifiers
        • View & Pure Modifiers
        • Data Types
          • Modifiers
          • Modifiers (Functions)
          • Address & Address Payable
        • Hardhat
        • Payable Functions
        • Receive Function
        • Fallback Function
        • Global Variables
        • Self Destruct
        • Create2 Function
        • Revert function
        • Require function
        • Assert Function
        • Calldata
        • Interface
        • Mapping
        • Array
        • Struct
        • Inheritance
          • Virtual & Overwrite
          • Multiple inheritance
          • Hierarchical Inheritance
        • Events
          • Indexed (keyword)
          • LOG0 - LOG4
        • Multi-signature Example
        • Smart Contracts
          • Context
      • Application Binary Interface (ABI )
  • Extras
    • Terminology
      • Bytecode
      • Keccak-256
      • Turing complete
Powered by GitBook
On this page
  1. General
  2. What is Ethereum
  3. Tries

Transactions Trie

The Transactions Trie in Ethereum is a Merkle Patricia Tree (also known as a radix tree) that stores information about all the transactions in the blockchain. Each node in the tree represents a hash of a key-value pair, where the key is the hash of the transaction and the value is the transaction itself.

The Transactions Trie is structured in a similar way to the State Trie, with each node in the tree representing a portion of the hash of the key. However, instead of storing account state information, the Transactions Trie stores information about each individual transaction.

When a new transaction is submitted to the Ethereum network, it is first validated by the nodes on the network, and then added to the Transactions Trie. The transaction is added to the Trie by hashing its transaction ID, and then adding it as a key-value pair in the Trie. The transaction itself is stored as the value for the corresponding key.

The Transactions Trie is used by the Ethereum network to keep track of all transactions that have been submitted and processed by the network. When a new block is added to the blockchain, it contains a list of all the transactions that were included in that block. The Transactions Trie is used to validate that the list of transactions in the new block matches the state of the network, and that there are no conflicting transactions or double-spending attempts.

PreviousStorage TrieNextReceipts Trie

Last updated 2 years ago