Has the contract been deployed?

I am getting an ok result but on blockchain explorer don’t see contract create tx under the contract address.

{ owner: ‘ak_2KZfUuD7Eay7mGghHzbhktocB8Czv2Nxejro6prpGZbq5WYafU’,
transaction: ‘th_2oixX6Wc5Xaq3x4vtajFQChRzgse4efemZnzeHHnQH3f1RPiTQ’,
address: ‘ct_DeRuk3os1AaoiNtpiHnX5GnUHCVhqgZP9uQnEdx1UzNMq65Pf’,
createdAt: 2019-12-28T15:07:12.238Z,
result:
{ callerId: ‘ak_2KZfUuD7Eay7mGghHzbhktocB8Czv2Nxejro6prpGZbq5WYafU’,
callerNonce: 1,
contractId: ‘ct_DeRuk3os1AaoiNtpiHnX5GnUHCVhqgZP9uQnEdx1UzNMq65Pf’,
gasPrice: 1000000000,
gasUsed: 134,
height: 189354,
log: [],
returnType: ‘ok’,
returnValue: ‘cb_Xfbg4g==’ },
rawTx: ‘tx_+QIzCwH4QrhABDjRo7IjX9sMsgtPaeAgpX7ewIHUMvUpchxaiGIC+ji90GXe24miV7lvr93ns63kPwWilC5PdoRRWaYT3liWB7kB6vkB5yoBoQGt2JVPDwkBDPeXKh8LQ8PM0Yktu6Baj28Hw5ekmNcwKQG5AaD5AZ1GA6B2WQIjYi7VbZEWpqC4ZAdW+nZ676uZwf8UY4mFRG0ntcC5AW+5ATP+RNZEHwA3ADcAKgAMAwAqACcMBg8CggEDP/5y9wMQADcBRwAHKCwEgizQAAAA/qZTuAAANwhHAJdvAAd3d3cHBwcgNAYhcG9zdFRhc2sHDAoMA38GAwQHDAj7A9FXcm9uZyBmdW5jdGlvbiBuYW1lLCBub25jZSBvciBmYWlsZWQgc2lnbmF0dXJlIGNoZWNrDAEAOAAMAQgMAQoMAQwMAQ4MAwAnDA4PAgIoLgYAgigsAoItiAYCKS6CAIIoLAKCECkuggKCKC4KBIIoLASCLNAAABAtGAoAKS6CBIIoLAKCEgA7BA47BAw6ADoECjoECDoEBjsEBDoAHQB0UAACBwwODAN/BgMEKCwEgizQAAAgBAQGAwT+6/IunAA3AQc3B0cAJwd3dwcHBygsAIIrEAAAtS8EEUTWRB8RaW5pdBFy9wMQIWdldE5vbmNlEaZTuAAhcG9zdFRhc2sR6/IunB1nZXRUYXNrgi8AhTQuMS4wAIMFAAOGTSAJ4IAAAAAAgxgX+IQ7msoAhysRRNZEHz+bka6Q’ }

1 Like

Also i was using this line to deploy: let result = await _contract.deploy([10000, 15]);
I am not sure if gas price / limit has been set correctly. I just used these values as have seen it somewhere, but I can’t find more detailed documentation. What do 10000 and 15 refer to?

Just an example of what I am looking at in block explorer.
So one random contract deploy tx that I found:

  • there is this mine block at the bottom

Now my deploy tx:

  • this mine block at the bottom is missing, even though the tx shows block height as 189354

It looks like the explorer has some sort of (caching?) issue… Here it looks fine: th_2oixX6Wc5Xaq3x4vtajFQChRzgse4efemZnzeHHnQH3f1RPiTQ of Aeternity - AEKnow

1 Like

Maybe @jsnewby can take a quick look at this as he is maintaining the aeternal.io explorer / middleware.

Hi there, super sorry but I don’t understand what the issue is?

The aeternal node was (for some reason) out of sync. It gave an error message (can’t remember the exact one) saying the chain wasn’t at height X when aeknow.org was a couple of hundred generations further on.

It might have resolved itself, this was six days ago…

Ah yes someone brought that to my attention, and I gave it a kick.