Opcode
An opcode (operation code) is a single low-level instruction that a blockchain's virtual machine can execute, such as adding two numbers, saving data or calling another contract. Smart contract bytecode is a sequence of opcodes.
On Ethereum and other EVM chains, each opcode is identified by a single byte, so the instruction set has at most 256 entries. Developers usually write in a high-level language like Solidity, and a compiler turns that code into bytecode made of opcodes such as ADD, SSTORE, CALL and REVERT. The EVM runs them in sequence using a stack. Values are pushed onto the stack, an operation consumes them, and the result is pushed back. Bitcoin Script uses opcodes too, such as OP_CHECKSIG.
Opcodes matter to everyday users because every EVM opcode has a set gas cost, and the opcodes a transaction executes determine how much gas it consumes. Writing to storage with SSTORE costs far more than simple arithmetic, which is one reason complex DeFi interactions carry higher fees.
Opcodes also appear on block explorers. When a swap fails because the price moved beyond the slippage tolerance, the contract executes REVERT and the explorer shows the returned error message. ETH sent by a contract through CALL is listed as an internal transaction. Proxy contracts use DELEGATECALL to run code stored in a separate implementation contract.
A common misconception is that a contract's published source code tells the whole story. What actually runs is the bytecode, and DELEGATECALL lets an upgradeable contract's behaviour change later. Unverified or obfuscated code can hide malicious logic, so the opcodes a contract uses are central to any security review.