Bytecode
Bytecode is the compact, machine-readable form of a smart contract that the Ethereum Virtual Machine (EVM) actually stores and executes. It is produced by compiling human-readable source code, such as Solidity, into a sequence of low-level instructions.
Developers write smart contracts in languages like Solidity, then a compiler translates that code into bytecode. Bytecode is a string of bytes, each representing an opcode (a basic instruction such as add, store or jump) or the data that instruction uses. When a contract is deployed, this bytecode is sent to the blockchain in a transaction and stored at a contract address, where every node can run it in the same way. Each opcode executed costs gas.
On a block explorer, bytecode appears as a long hexadecimal string. For example, many contracts compiled from Solidity begin with 0x6080604052, which decodes to a few opcodes that set up memory before the rest of the contract runs. Because raw bytecode is very hard for people to read, explorers let developers "verify" a contract by publishing source code that compiles to exactly the deployed bytecode.
Bytecode matters because it is what really runs, not the project's description of it. Comparing deployed bytecode with audited code, or checking whether a contract is verified at all, is a basic way to see what an app will do with funds.
A common misconception is that a verified contract is safe. Verification only proves the published source matches the bytecode; that code can still contain bugs, hidden fees or admin powers. Similarly, deployed bytecode cannot normally be edited, but a proxy contract can point to new logic, so behaviour can still change.