EVM (Ethereum Virtual Machine) blockchains do have timestamps, but they are associated with blocks rather than individual transactions. Here’s why:

• Block Timestamps: In EVM blockchains, each block has a single timestamp that represents the time when the block was mined1. This timestamp is set by the miner who successfully mines the block. Since all transactions in a block are considered to have occurred at the same time for the purposes of the blockchain, they inherit the block’s timestamp.
• Transaction Ordering: Transactions within a block are ordered by the miner, but they don’t have individual timestamps because the block timestamp serves as the time reference for all transactions within that block1.
• Immutability and Security: The block timestamp provides a secure and immutable reference point that can be audited and verified independently. It ensures that the entire block of transactions is accepted into the blockchain at a specific point in time2.
• Efficiency: Having a single timestamp for the entire block rather than individual timestamps for each transaction simplifies the data structure and reduces the amount of data stored on the blockchain. This contributes to the overall efficiency of the network2.
• Retrieving Event Logs: While individual transactions don’t have separate timestamps, events emitted by smart contracts during transactions are recorded in the receipt trie and can be retrieved along with the block timestamp for detailed analysis3.

In summary, the design of EVM blockchains prioritizes efficiency and security by using block timestamps as a collective time reference for all transactions within that block. Individual transaction timestamps are not necessary because the block timestamp serves the purpose of recording when the transactions were confirmed and added to the blockchain.