Sending transactions in Blockchain / Solidity - Time & Space Complexity

Time Complexity: Sending transactions

O(n)

Understanding Time Complexity

When sending transactions on a blockchain, it's important to understand how the time needed grows as more transactions are processed.

We want to know how the cost changes when sending many transactions one after another.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

function sendTransactions(transactions) {
  for (let i = 0; i < transactions.length; i++) {
    blockchain.send(transactions[i]);
  }
}
    

This code sends each transaction one by one to the blockchain network.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Sending a single transaction to the blockchain.
• How many times: Once for each transaction in the input list.

How Execution Grows With Input

As the number of transactions increases, the total sending time grows in direct proportion.

Input Size (n)	Approx. Operations
10	10 sends
100	100 sends
1000	1000 sends

Pattern observation: Doubling the number of transactions doubles the total sending time.

Final Time Complexity

Time Complexity: O(n)

This means the time to send transactions grows linearly with the number of transactions.

Common Mistake

[X] Wrong: "Sending multiple transactions at once takes the same time as sending one."

[OK] Correct: Each transaction requires its own processing time, so more transactions mean more total time.

Interview Connect

Understanding how sending transactions scales helps you explain performance in blockchain apps clearly and confidently.

Self-Check

"What if we batch multiple transactions into one send call? How would the time complexity change?"

Practice

1.

What is the main purpose of sending a transaction on a blockchain?

easy

A. To create a new blockchain network

B. To mine new blocks

C. To move value or data from one account to another

D. To delete data from the blockchain

Solution

1. Step 1: Understand what a transaction does

   A transaction moves value or data between accounts on the blockchain.

2. Step 2: Compare options to the definition

   Only To move value or data from one account to another correctly describes sending a transaction.

3. Final Answer:

   To move value or data from one account to another -> Option C

4. Quick Check:

   Transaction purpose = move value/data [OK]

Hint: Transactions move value or data, not create or delete [OK]

Common Mistakes:

• Confusing transactions with mining
• Thinking transactions create blockchains
• Believing transactions delete blockchain data

2.

Which of the following is the correct way to sign a transaction before sending it?

transaction.sign(____)

easy

A. sender's public key

B. sender's private key

C. receiver's private key

D. network's public key

Solution

1. Step 1: Identify the key needed for signing

   Transactions must be signed with the sender's private key to prove ownership.

2. Step 2: Match the correct key to the method

   Only the sender's private key can sign the transaction securely.

3. Final Answer:

   sender's private key -> Option B

4. Quick Check:

   Sign with private key = sender's private key [OK]

Hint: Sign with sender's private key, never public key [OK]

Common Mistakes:

• Using public key to sign
• Using receiver's key instead of sender's
• Confusing private and public keys

3.

Consider this code snippet sending a transaction:

tx = {
  'to': '0xabc123',
  'value': 10,
  'nonce': 5,
  'gas': 21000
}
signed_tx = sign_transaction(tx, private_key)
result = send_transaction(signed_tx)
print(result)

What will print(result) most likely output if the nonce is incorrect?

medium

A. 'Nonce too low or too high error'

B. 'Transaction successful'

C. 'Gas limit exceeded error'

D. 'Invalid signature error'

Solution

1. Step 1: Understand nonce role in transactions

   Nonce must be correct and sequential to avoid replay or duplication errors.

2. Step 2: Identify error caused by wrong nonce

   An incorrect nonce causes a 'Nonce too low or too high' error during sending.

3. Final Answer:

   'Nonce too low or too high error' -> Option A

4. Quick Check:

   Wrong nonce = nonce error [OK]

Hint: Wrong nonce causes nonce error, not gas or signature errors [OK]

Common Mistakes:

• Confusing nonce error with gas error
• Assuming signature error for nonce issues
• Expecting success despite wrong nonce

4.

Given this code snippet, what is the main error preventing the transaction from sending?

tx = {
  'to': '0xdef456',
  'value': 5,
  'nonce': 3
}
signed_tx = sign_transaction(tx, private_key)
result = send_transaction(signed_tx)
print(result)

Options:

medium

A. Receiver address is invalid

B. Incorrect private key used for signing

C. Nonce value is too high

D. Missing gas field in the transaction

Solution

1. Step 1: Check required transaction fields

   Gas is required to pay for transaction processing; missing gas causes failure.

2. Step 2: Verify other fields and keys

   Nonce and receiver address look valid; no info about wrong private key.

3. Final Answer:

   Missing gas field in the transaction -> Option D

4. Quick Check:

   Missing gas = transaction fails [OK]

Hint: Always include gas field to avoid transaction failure [OK]

Common Mistakes:

• Ignoring gas field requirement
• Assuming nonce or address is wrong without evidence
• Not checking transaction structure

5.

You want to send multiple transactions quickly from the same account. Which approach ensures all transactions are accepted without nonce conflicts?

1. Use the same nonce for all transactions
2. Increment nonce by 1 for each transaction
3. Use random nonce values
4. Skip nonce and rely on network

hard

A. Increment nonce by 1 for each transaction

B. Skip nonce and rely on network

C. Use random nonce values

D. Use the same nonce for all transactions

Solution

1. Step 1: Understand nonce role in multiple transactions

   Nonce must be unique and sequential per account to avoid conflicts.

2. Step 2: Identify correct nonce handling method

   Incrementing nonce by 1 for each transaction ensures proper ordering and acceptance.

3. Final Answer:

   Increment nonce by 1 for each transaction -> Option A

4. Quick Check:

   Sequential nonce = no conflicts [OK]

Hint: Always increment nonce by 1 for each new transaction [OK]

Common Mistakes:

• Reusing same nonce causing rejection
• Using random nonce causing errors
• Assuming network assigns nonce automatically