Event Log
An event log is a record that a smart contract emits during a transaction to announce that something happened, such as a token transfer or swap. Logs are stored in the transaction receipt for wallets, explorers and apps to read.
On Ethereum and other EVM-compatible chains, a contract emits an event using dedicated log opcodes. Each log records the emitting contract's address, up to four indexed 'topics' and a data field. The first topic is usually a hash of the event's signature, and the remaining fields carry details like addresses and amounts. Logs are kept in transaction receipts rather than contract storage, which makes them cheaper to write. Other contracts cannot read them.
Event logs are how most crypto software knows what happened. Wallets, block explorers and analytics tools scan logs to build token balances, transaction histories and alerts without re-running every transaction. On a block explorer, the Logs tab of a transaction acts as an itemised record of each step in a complex interaction.
For example, every standard ERC-20 transfer emits a Transfer event listing the sender, recipient and amount. A single DeFi swap might produce several Transfer events plus a Swap event from the pool, showing exactly how tokens moved.
The main misconception is that logs are the source of truth. They only report what a contract chooses to emit, and the actual balances live in contract storage. A malicious contract can emit fake Transfer events naming any address. Address poisoning exploits this by planting look-alike addresses in a victim's history, so verifying full addresses before sending matters.