0

I created a contract.

https://ropsten.etherscan.io/tx/0x74426948905cd6e70e8b9d64a660b3c179b7c8a224ca5cd0234842768eb501db

I can see the input Data in hex on etherscan. How can I decode from this? I want to see the raw contract or contract code so that I can confirm whether my contract is correct or not.

3
  • Are you sure that transaction is correct? Here is an example of a transaction to a contract in Etherscan.io: etherscan.io/tx/… . The "to" is recognized as a contract. Note that you might have the correct transaction; I'm just shooting in the dark.
    – lungj
    Commented Jul 17, 2017 at 14:07
  • @lungj seems my contract transaction is wrong. I will deploy again. Thank you for your reply.
    – zono
    Commented Jul 17, 2017 at 14:15
  • @lungj You answered on my question exactly. If you post your answer I wil accept it. (stack exchange community may want to it to close this question)
    – zono
    Commented Jul 17, 2017 at 14:23

2 Answers 2

2

The transaction you point to did not create a contract (called deploying).

Did you use Mist or Parity wallet to 'deploy' the contract or did you simply send the byte data to an address via geth command line?

If you were trying to deploy the contract code, the to field would be 0x0. Because to is not 0x0 but just a regular (non-contract) account, the byte data in the input field is simply ignored (although it can be interpreted as a message).

If to is not 0x0 you aren't deploying a contract. If the address was a contract, Etherscan would indicate as much.

2
  • Thank you. As you said, my deploying was wrong. I deploy with sendrawtransaction. At that time, I put the wrong value into "to" param. My deploying was described on another my question. ethereum.stackexchange.com/questions/21428/…
    – zono
    Commented Jul 17, 2017 at 15:30
  • 1
    Yes. A deployment will always be to 0x0. You should select my answer so others are not confused. Commented Jul 17, 2017 at 15:34
1

Are you sure that transaction is correct? Here is an example of a transaction to a contract in Etherscan.io. The "to" is recognized as a contract. Note that you might have the correct transaction; I'm just shooting in the dark.

3
  • I don't understand why this answer was accepted. It doesn't answer the question. The trouble is that no contract was deployed as one can tell given that the to address is not a contract. I suspect the OP incorrectly sent byte code to an 'regular' address under the assumption that this was how one deploys a contract, which is not correct. Commented Jul 17, 2017 at 15:27
  • The example link was for sending to a contract (which contrasts with OP's sending to a regular address).
    – lungj
    Commented Jul 17, 2017 at 15:30
  • OP says "I create a contract" and then points to creation transaction. The to address of a deployment should be '0x0'. I read the OP's original post (and other posts by same author) as saying that he deployed with the referenced transaction. (Which he/she didn't.) The same author posted this question (ethereum.stackexchange.com/questions/21428/…) which has the same problem of no deployment. Commented Jul 17, 2017 at 15:31

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.