Blok
Zincirin bir birimini oluşturan işlemler konteyneri.
Blocks are the 'pages' of the blockchain ledger. Each block contains a bundle of verified transactions, a timestamp, a reference to the previous block (Parent Hash), and a solution to a cryptographic puzzle (in Proof of Work) or a validator's signature (in Proof of Stake). This chaining mechanism ensures that to modify an old block, you would have to redo the work for all subsequent blocks, making the history immutable.
graph LR
Center["Blok"]:::main
Pre_transaction["transaction"]:::pre --> Center
click Pre_transaction "/terms/transaction"
Pre_hashing["hashing"]:::pre --> Center
click Pre_hashing "/terms/hashing"
Pre_merkle_tree["merkle-tree"]:::pre --> Center
click Pre_merkle_tree "/terms/merkle-tree"
Rel_blockchain["blockchain"]:::related -.-> Center
click Rel_blockchain "/terms/blockchain"
Rel_mining["mining"]:::related -.-> Center
click Rel_mining "/terms/mining"
Rel_consensus_mechanism["consensus-mechanism"]:::related -.-> Center
click Rel_consensus_mechanism "/terms/consensus-mechanism"
classDef main fill:#7c3aed,stroke:#8b5cf6,stroke-width:2px,color:white,font-weight:bold,rx:5,ry:5;
classDef pre fill:#0f172a,stroke:#3b82f6,color:#94a3b8,rx:5,ry:5;
classDef child fill:#0f172a,stroke:#10b981,color:#94a3b8,rx:5,ry:5;
classDef related fill:#0f172a,stroke:#8b5cf6,stroke-dasharray: 5 5,color:#94a3b8,rx:5,ry:5;
linkStyle default stroke:#4b5563,stroke-width:2px;
🧒 5 yaşındaki gibi açıkla
📦 Bir blok, onaylanmış işlemlerin bir listesini tutan, bir öncekinden zincirlenmiş, bir defterdeki güvenli bir dijital sayfa gibidir.
🤓 Expert Deep Dive
## Expert Deep Dive: Block
A block in distributed ledger technologies is a cryptographically secured, immutable data structure containing a batch of validated transactions. Its fundamental role is to serve as a sequential unit within a blockchain, ensuring the integrity and chronological ordering of ledger entries. Each block is intrinsically linked to its predecessor via a cryptographic hash, forming the chain. This linkage, coupled with the block's internal structure, establishes immutability; any alteration to a prior block invalidates all subsequent blocks.
A block's typical composition includes a block header and transaction data. The header, critical for validation and chaining, comprises metadata such as the hash of the previous block, a timestamp, a nonce (in Proof-of-Work systems), and a Merkle root. The Merkle root, a cryptographic summary of all transactions within the block, enables efficient verification of transaction inclusion. The transaction data section contains the actual, confirmed transactions.
Block creation and inclusion are governed by consensus mechanisms (e.g., Proof-of-Work, Proof-of-Stake), dictating the rules for block generation and validation by network participants. Rigorous validation ensures hash difficulty targets are met, transactions are valid, and the previous block hash is correctly referenced. Block size limits are imposed to manage network propagation and congestion. In many systems, block producers are incentivized via block rewards and transaction fees. Furthermore, in systems supporting smart contracts, a block represents a state transition, updating the ledger's global state through the execution of its contained transactions.