Blocks, chains, and hashing in Blockchain / Solidity - Time & Space Complexity
When working with blocks and chains in blockchain, it is important to understand how the time to process data grows as the chain gets longer.
We want to know how the time to add or verify blocks changes as more blocks join the chain.
Analyze the time complexity of the following code snippet.
function verifyChain(chain) {
for (let i = 1; i < chain.length; i++) {
if (chain[i].previousHash !== hash(chain[i - 1])) {
return false;
}
}
return true;
}
This code checks if each block correctly links to the previous one by comparing hashes along the chain.
- Primary operation: Looping through each block in the chain to check hashes.
- How many times: Once for each block except the first, so roughly the number of blocks (n).
As the chain grows, the time to verify it grows in a straight line with the number of blocks.
| Input Size (n) | Approx. Operations |
|---|---|
| 10 | About 9 hash checks |
| 100 | About 99 hash checks |
| 1000 | About 999 hash checks |
Pattern observation: Doubling the number of blocks roughly doubles the work needed.
Time Complexity: O(n)
This means the time to verify the chain grows directly with the number of blocks.
[X] Wrong: "Verifying the chain takes the same time no matter how long it is."
[OK] Correct: Each block must be checked against the previous one, so more blocks mean more checks and more time.
Understanding how verification time grows helps you explain blockchain efficiency clearly and confidently in real-world discussions.
"What if we stored a summary hash that represents the whole chain? How would the time complexity of verification change?"
Practice
Solution
Step 1: Understand what a hash does
A hash is a unique code generated from the block's data, like a fingerprint.Step 2: Identify the purpose of the hash in blockchain
The hash ensures the block's data cannot be changed without detection.Final Answer:
To create a unique fingerprint of the block's data -> Option AQuick Check:
Hash = Unique fingerprint [OK]
- Confusing hash with timestamp
- Thinking hash stores transactions
- Believing hash connects to internet
Solution
Step 1: Recognize the correct hash function usage
SHA256 is a common hash function applied to block data to get the hash.Step 2: Check each option for correct syntax
hash = SHA256(block_data) correctly applies SHA256 to block_data. Others misuse the function or syntax.Final Answer:
hash = SHA256(block_data) -> Option BQuick Check:
Correct hash function call = hash = SHA256(block_data) [OK]
- Adding hash function as string instead of calling it
- Using incorrect syntax for hash function
- Confusing method call with variable
import hashlib block_data = 'Block 1 data' hash_object = hashlib.sha256(block_data.encode()) block_hash = hash_object.hexdigest() print(block_hash)What will be the output type of
block_hash?Solution
Step 1: Understand hashlib.sha256 and hexdigest()
hashlib.sha256 returns a hash object; hexdigest() converts it to a hex string.Step 2: Identify the output type of hexdigest()
hexdigest() returns a string representing the hash in hexadecimal form.Final Answer:
string -> Option CQuick Check:
hexdigest() output = string [OK]
- Thinking hexdigest() returns bytes
- Confusing output with integer or list
- Ignoring .encode() usage
class Block:
def __init__(self, data, prev_hash):
self.data = data
self.prev_hash = prev_hash
block1 = Block('First block', None)
block2 = Block('Second block', block1.hash)
Solution
Step 1: Check block1 attributes
block1 has data and prev_hash but no attribute named 'hash'.Step 2: Identify usage of undefined attribute
block2 tries to use block1.hash which does not exist, causing an error.Final Answer:
block1.hash is not defined before use -> Option AQuick Check:
Accessing undefined attribute = block1.hash is not defined before use [OK]
- Assuming hash attribute exists by default
- Confusing prev_hash type requirements
- Thinking data type causes error
Solution
Step 1: Check hash calculation includes previous hash
The correct implementation computes the hash from both data and prev_hash:self.hash = hashlib.sha256((data + prev_hash).encode()).hexdigest(), ensuring secure linking.Step 2: Verify other options
B: prev_hash set after hash computation (hash ignores prev_hash); C: no hashing, just concatenation; D: hash ignores prev_hash.Final Answer:
self.hash = hashlib.sha256((data + prev_hash).encode()).hexdigest() -> Option DQuick Check:
Hash(data + prev_hash) [OK]
- Not including prev_hash in hash calculation
- Assigning prev_hash after block creation
- Using plain concatenation without hashing
Ready to prove it?
Pass the test and this pattern moves unknown
