_ Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top up vote down vote favorite 5 I'm syncing up a new node.How can I find out what the latest block is so that I know how far I've got to go?nodes synchronization up vote down vote For Geth, in another terminal, attach to the Geth console, such as geth attach.This will allow you to keep your syncing node running, without restarting, and you will not see the noisy logs as you would if you simply ran "geth console" without other parameters.In the console, run eth.syncing > eth.syncing { currentBlock: 745600, highestBlock: 889152, startingBlock: 745553 } You can then see where you are (currentBlock), and the block you still have to reach (highestBlock).(The difference between them is the number of blocks you have left remaining.)You can run eth.syncing a few times to check your progress, and it will return false when done.

You can then use eth.blockNumber and also compare with a blockchain explorer, as other answers here mention.up vote 8 down vote If you are using Geth: stop your current instance of geth, then re-run it with the console argument: geth console then enter: web3.eth.blockNumber It will give you the block number as integer, here's the function documentation.If you are looking for the block hash instead you can use: web3.eth.getBlock(BLOCK_NUMBER).hash so for the current block (atm) it will be: web3.eth.getBlock(887893).hash and for the latest block: web3.eth.getBlock(web3.eth.blockNumber).hash up vote 6 down vote You could use a block explorer, such as Etherchain.up vote 5 down vote The Ethereum wallet will display the latest block number.The official Ethereum stats website also displays it.(Note: this doesn't represent all peers on the network.)up vote 3 down vote web3.eth.blockNumber gets you the latest block height on your node.

Note that you have to have a synced node for that.When you are still downloading the blockchain this number will be smaller.up vote 2 down vote If you are still syncing you can type eth.syncing and it will report currentBlock highestBlock startingBlock If eth.syncing is false then use the eth.blockNumber command sebastian mentioned and compare it to the reported block height from your favorite online block explorer up vote 2 down vote /lyricalpolymath/Ethereum-Scripts 1) show simple progress % with geth running, copy and paste this code in a terminal window to have a simple feedback of the blockchain syncing progress geth --exec 'var s = eth.syncing; console.log(" ------------ GETH SYNCING PROGRESS progress: " + (s.currentBlock/s.highestBlock*100)+ " % blocks left to parse: "+ (s.highestBlock-s.currentBlock) + " current Block: " + s.currentBlock + " of " + s.highestBlock)' attach you will get an output like this ------------ GETH SYNCING PROGRESS progress: 81.9161292631709 % blocks left to parse: 368837 current Block: 1670754 of 2039591 2) advance progress with Time Estimate download the script and with geth running, copy and paste this code in a terminal window to have a simple feedback of the blockchain syncing progress geth --exec "loadScript('GethSyncingProgress_2TimeEstimate.js')" attach will give you an output like ------------ GETH SYNCING PROGRESS - Time estimate progress: 83.83513931320763 Estimated Time left*: 7d :11h :4m :4s.3 Time it took to parse 10 blocks: 0d :0h :0m :19s.5 blocks left to parse: 330536 Your Answer Sign up or log in Sign up using Google Sign up using Email and Password Post as a guest Name Email discard By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged nodes synchronization or ask your own question.Last blocks sample 30 minutes Avg Block Time seconds Transactions Per Block Amount Transfered Ether Amount Per Block Ether Gas Used Avg Gas Price MWei Blockchain Height Difficulty TH Hashrate GH/s Price Coins Price Per ETC USD Market Cap USD Latest Blocksbitcoin order book depthEthereum implements a javascript runtime environment (JSRE) that can be used in either interactive (console) or non-interactive (script) mode.ethereum replacementEthereum's Javascript console exposes the full web3 JavaScript Dapp API and the admin API.bitcoin legal aspects

The ethereum CLI executable geth has a JavaScript console (a Read, Evaluate & Print Loop = REPL exposing the JSRE), which can be started with the console or attach subcommand.The console subcommands starts the geth node and then opens the console.godaddy bitcoinThe attach subcommand will not start the geth node but instead tries to open the console on a running geth instance.litecoin trendThe attach node accepts an endpoint in case the geth node is running with a non default ipc endpoint or you would like to connect over the rpc interface.ethereal blade lionNote that by default the geth node doesn't start the http and weboscket service and not all functionality is provided over these interfaces due to security reasons.ethereum casino

These defaults can be overridden when the --rpcapi and --wsapi arguments when the geth node is started, or with admin.startRPC and admin.startWS.If you need log information, start with: Otherwise mute your logs, so that it does not pollute your console: Geth has support to load custom JavaScript files into the console through the --preload argument.bitcoin mining for nvidiaThis can be used to load often used functions, setup web3 contract objects, or ... It's also possible to execute files to the JavaScript interpreter.bitcoin boston maThe console and attach subcommand accept the --exec argument which is a javascript statement.This prints the current block number of a running geth instance.Or execute a local script with more complex statements on a remote node over http: Find an example script here Use the --jspath to set a libdir for your js scripts.

Parameters to loadScript() with no absolute path will be understood relative to this directory.You can exit the console cleanly by typing exit or simply with CTRL-C.The go-ethereum JSRE uses the Otto JS VM which has some limitations: Note that the other known limitation of Otto (namely the lack of timers) is taken care of.Ethereum JSRE implements both setTimeout and setInterval.In addition to this, the console provides admin.sleep(seconds) as well as a "blocktime sleep" method admin.sleepBlocks(number).Since web3.js uses the bignumber.js library (MIT Expat Licence), it is also autoloded.In addition to the full functionality of JS (as per ECMA5), the ethereum JSRE is augmented with various timers.It implements setInterval, clearInterval, setTimeout, clearTimeout you may be used to using in browser windows.It also provides implementation for admin.sleep(seconds) and a block based timer, admin.sleepBlocks(n) which sleeps till the number of new blocks added is equal to or greater than n, think "wait for n confirmations".

Beside the official DApp API interface the go ethereum node has support for additional management API's.These API's are offered using JSON-RPC and follow the same conventions as used in the DApp API.The go ethereum package comes with a console client which has support for all additional API's.It is possible to specify the set of API's which are offered over an interface with the --${interface}api command line argument for the go ethereum daemon.Where ${interface} can be rpc for the http interface or ipc for an unix socket on unix or named pipe on Windows.For example, geth --ipcapi "admin,eth,miner" --rpcapi "eth,web3" will Please note that offering an API over the rpc interface will give everyone access to the API who can access this interface (e.g.So be careful which API's you enable.By default geth enables all API's over the ipc interface and only the eth,net and web3 API's over the rpc and ws interface.To determine which API's an interface provides the modules transaction can be used, e.g.

over an ipc interface on unix systems: will give all enabled modules including the version number: These additional API's follow the same conventions as the official DApp API.Web3 can be extended and used to consume these additional API's.The different functions are split into multiple smaller logically grouped API's.Examples are given for the Javascript console but can easily be converted to a rpc request.IPC: echo '{"jsonrpc":"2.0","method":"miner_start","params":[],"id":1}' | socat -,ignoreeof UNIX-CONNECT:$HOME/.ethereum/geth.ipc RPC: curl -X POST --data '{"jsonrpc":"2.0","method":"miner_start","params":[],"id":74}' localhost:8545 With the number of THREADS as an arguments: IPC: echo '{"jsonrpc":"2.0","method":"miner_start","params":["0x04"],"id":1}' | socat -,ignoreeof UNIX-CONNECT:$HOME/.ethereum/geth.ipc RPC: curl -X POST --data '{"jsonrpc":"2.0","method":"miner_start","params":["0x04"],"id":74}' localhost:8545 The personal api exposes method for personal the methods to manage, control or monitor your node.

It allows for limited file system access.Create a new password protected account string address of the new account personal.newAccount() # will prompt for the password Unlock the account with the given address, password and an optional duration (in seconds).If password is not given you will be prompted for it.boolean indication if the account was unlocked The admin exposes the methods to manage, control or monitor your node.To connect to a node, use the enode-format nodeUrl as an argument to addPeer or with CLI param bootnodes.Pass a nodeURL to connect a to a peer on the network.The nodeURL needs to be in enode URL format.geth will maintain the connection until it shuts down and attempt to reconnect if the connection drops intermittently.You can find out your own node URL by using nodeInfo or looking at the logs when the node boots up e.g.: an array of objects with information about connected peers.Imports the blockchain from a marshalled binary format.Note that the blockchain is reset (to genesis) before the imported blocks are inserted to the chain.

true on success, otherwise false.Exports the blockchain to the given file in binary format.Starts the HTTP server for the JSON-RPC.Stops the HTTP server for the JSON-RPC.Starts the websocket server for the JSON-RPC.Stops the websocket server for the JSON-RPC.the directory this nodes stores its data a string describing the compiler version when path was valid, otherwise an error activate NatSpec: when sending a transaction to a contract, Registry lookup and url fetching is used to retrieve authentic contract Info for it.It allows for prompting a user with authentic contract-specific confirmation messages.deactivate NatSpec: when sending a transaction, the user will be prompted with a generic confirmation message, no contract info is fetched this will retrieve the contract info json for a contract on the address returns the contract info object will write contract info json into the target file, calculates its content hash.This content hash then can used to associate a public url with where the contract info is publicly available and verifiable.

If you register the codehash (hash of the code of the contract on contractaddress).contenthash on success, otherwise undefined.will register content hash to the codehash (hash of the code of the contract on contractaddress).The register transaction is sent from the address in the first parameter.The transaction needs to be processed and confirmed on the canonical chain for the registration to take effect.this will register a contant hash to the contract' codehash.This will be used to locate contract info json files.Address in the first parameter will be used to send the transaction./ethereum/go-ethereum/wiki/Mining) on with the given threadNumber of parallel threads.This is an optional argument.Starts automatic pregeneration of the ethash DAG.This process make sure that the DAG for the subsequent epoch is available allowing mining right after the new epoch starts.If this is used by most network nodes, then blocktimes are expected to be normal at epoch transition.Auto DAG is switched on automatically when mining is started and switched off when the miner stops.

Stops automatic pregeneration of the ethash DAG.Auto DAG is switched off automatically when mining is stops.Generates the DAG for epoch blockNumber/epochLength.dir specifies a target directory, If dir is the empty string, then ethash will use the default directories ~/.ethash on Linux and MacOS, and ~\AppData\Ethash on Windows.The DAG file's name is full-R- true on success, otherwise false.Sets the extra data for the block when finding a block.Limited to 32 bytes.Sets the the gasprice for the miner Sets the the ether base, the address that will receive mining rewards.Sets the current head of the blockchain to the block referred to by blockNumber.See web3.eth.getBlock for more details on block fields and lookup by number or hash.Returns the hash for the epoch the given block is in.Returns the hexadecimal representation of the RLP encoding of the block.The hex representation of the RLP encoding of the block.Prints information about the block such as size, total difficulty, as well as header fields properly formatted.