I was trying to deploy a contract to public ethereum network using Mist. I was able to send transaction successfully but my transaction is get no confirmations. It has been around 45 minutes and my transaction is still on 0 out of 12 confirmations. What could be the possible reason?


  • I have sufficient ethers in my account (more than 1)

  • I have tested the contracted on private testnet.

  • My ethereum node is not synced to blockchain (still 142882 blocks to go)

  • I have let Mist decide the fee for transaction.

Edit :
On Private-test Network:

  • Estimated fee consumption=0.02485106 ether (1242553 gas)

  • Provided max fee= 0.02685106 ether (1342553 gas)

  • Gas used: 1243385

On Public net:

  • Estimated fee: 1275193 gas

  • Provided Max fee: 1375193 gas

  • Gas used: 1375193

Also when I tried to track whether my transaction ran out of Gas using ether.camp, it could not find my transaction, same was with Etherscan.How even can I track my transaction?

Edit 2:
Mist stopped syncing at block 2283415, it is unable to download more peers from past 17 hours. I guess this may be a possible reason of why my transaction is not yet mined.

  • When deploying on your private network, what is the gas cost? The reason why I'm asking is that the gas limit on the public network has been set to a lower level to reduce the impact of the ongoing spam transactions since the start of Devcon2 a few weeks ago. From Ethereum Network Status, the gas limit is currently 1,485,443. See also The Ethereum network is currently undergoing a DoS attack. Commented Oct 12, 2016 at 12:54
  • I have edited the question. As I noticed on public net on clicking the transaction in latest Transaction tab, the gas used appears to be same as max gas provided, But the transaction has no confirmations yet. Has my contract deployment transaction ran out of gas? Commented Oct 13, 2016 at 4:05
  • perhaps it is because the Ddos attack
    – Badr Bellaj
    Commented Oct 13, 2016 at 6:56

1 Answer 1


Finally my contract is deployed. Actually it was due to DDOS attack and many people were facing same kind of issue. After the hard fork based on EIP 150 version 1c, my transaction went through automatically yesterday (October 18). I am waiting for blocckckchain to sync to the block in which my contract was deployed so that I could verify if it is working fine.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.