Bitcoin Sign up or log in to customize your list._ 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 0 down vote favorite Is there any Web API available for us to query Blockchain data in hex format?The format should follow the standard (https://en.bitcoin.it/wiki/Block#Block_structure) structure rather than JSON.blockchain raw-data up vote 3 down vote What kind of API do you want?Do you mean API with your local Bitcoin Core or do you need web-API?/block/000000000000000001f942eb4bfa0aeccb6a14c268f4c72d5fff17270da771b9 (this is an example) It is possible to download block as [json] / [hex] / [binary] there if you know the hash of the block 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.

Not the answer you're looking for?Browse other questions tagged blockchain raw-data or ask your own question.klienta bitcoinJump to: , Bitcoin Block Explorer is an online block chain browser which displays the contents of individual Bitcoin blocks and transactions and the transaction histories and balances of addresses.acquistare bitcoin euroIt was originally written by theymos, but it is now operated by Liraz Siri.bitcoin turfEach object is displayed in human-readable form, as a web page, and is given a URL.sabadell bitcoinBy using hyperlinks, it allows users to switch from seeing one piece of data to a related one, with a single click.cara buka bitcoin

Clicking on the hash of an object, will move to the page that displays its data.litecoin wiki poolsThis way for instance, you can switch from looking at a transaction, to looking at the previous transaction which gave this transaction its inputs.All block data is visible, in human-readable or machine-readable forms, and even some information that is not actually part of blocks.It is mainly aimed at advanced users who already know what blocks are and what kind of information they contain, but a lot of helpful information is provided in tool-tips.A listing of "strange transactions" is displayed in the main page, along with listings of the latest and largest transactions.Bitcoin Block Explorer can also display information from the Testnet.Contents 1 2 3 4 Many of the real-time stats pages existed before Bitcoin Block Explorer at http://theymos.ath.cx:64150/q.getdifficulty and getblockcount were created around July 2010, with decimaltarget, probability, hashestowin, nextretarget, totalbc, and bcperblock coming soon after.

These pages were made in response to block and difficulty values being "hard-coded" into text on the old wiki, which quickly made the information obsolete.Bitcoin Block Explorer was first made available around November 2010 at http://theymos.ath.cx:64150/bbe.It was initially meant to be the Bitcoin equivalent of TorStatus, dumping all important data about the network.Use the query pages such as getreceivedbyaddress wherever possible.Note that these pages do not send a trailing newline, which may cause problems with your HTTP-fetching tool.When an error occurs, the result will begin with "ERROR:", followed by the error text.Your detection of "ERROR" must be case-insensitive.An empty result is also an error.Non-fatal errors will print query results on the next line after the error, though using this data is inadvisable.To get block or transaction info, first find the hash of the item.This is done by using the search tool, which is accessible through a GET/HEAD request.For example, to get the hash of block number 444: $ 80 HEAD /search/444 HTTP/1.1 HTTP/1.1 302 Found ... /block/00000000cff43a64ec00bea1...

The hash is in the URL listed in the "location" header.Use it to get the JSON raw block: Transactions use a URL like this: If the search returns any status code other than 302, then the search is bad.A status code of 200 indicates that the search was ambiguous, and the page body will contain links to the choices.Example of search ambiguity.A search with no search terms will 302-redirect to the home page.Searches for valid block numbers will always redirect to the block with that number (ignoring all other search types), though you can force BBE to assume a hex value by preceding it with "0x".The shortlinks at the top of most pages are similar to searches.It is possible for shortlinks to be ambiguous, and they will likewise return a 200 status code in that case.Unfortunately, the JSON raw block/tx pages omit a lot of important information, and there is no similar page for addresses.A full XML interface is planned.Scraping the HTML pages is not recommended, as the layout can change at any time.

Jump to: , The data directory is the location where Bitcoin's data files are stored, including the wallet data file.Contents 1 2 3 4 5 Go to Start -> Run (or press WinKey+R) and run this: Bitcoin's data folder will open.For most users, this is the following locations: "AppData" and "Application data" are hidden by default.You can also store Bitcoin data files in any other drive or folder.If you have already downloaded the data then you will have to move the data to the new folder.If you want to store them in D:\BitcoinData then click on "Properties" of a shortcut to bitcoin-qt.exe and add -datadir=D:\BitcoinData at the end as an example: Start Bitcoin, now you will see all the files are created in the new data directory.By default Bitcoin will put its data here: You need to do a "ls -a" to see directories that start with a dot.If that's not it, you can do a search like this: By default Bitcoin will put its data here: An overview of these is in [files.md] in the Bitcoin Core documentation.

The data, index and log files are used by Oracle Berkeley DB, the embedded key/value data store that Bitcoin uses.Contains testnet versions of these files (if running with -testnet) [v0.8 and above] Contains blockchain data.[v0.8 and above] A LevelDB database with a compact representation of all currently unspent transaction outputs and some metadata about the transactions they are from.The data here is necessary for validating new incoming blocks and transactions.It can theoretically be rebuilt from the block data (see the -reindex command line option), but this takes a rather long time.Without it, you could still theoretically do validation indeed, but it would mean a full scan through the blocks (7 GB as of may 2013) for every output being spent.[v0.8 and above] Contains "undo" data.You can see blocks as 'patches' to the chain state (they consume some unspent outputs, and produce new ones), and see the undo data as reverse patches.They are necessary for rolling back the chainstate, which is necessary in case of reorganizations.

There is a torrent file that gets updated every few months that enables a much faster download of the blockchain.Once downloaded, the bootstrap.dat file can be placed in the root of the data directory, and Bitcoin Core 0.7.1 and above will automatically import it.NOTE: As of Bitcoin Core version 0.10.0 and later, the blockchain bootstrap torrent is slower than a direct download using the bitcoin P2P protocol & client.[2]This section may be of use to you if you wish to send a friend the blockchain, avoiding them a hefty download.Other files and folders (blocks, blocks/index, chainstate) may be safely transferred/archived as they contain information pertaining only to the public blockchain.The database files in the "blocks" and "chainstate" directories are cross-platform, and can be copied between different installations.These files, known collectively as a node's "block database", represent all of the information downloaded by a node during the syncing process.In other words, if you copy installation A's block database into installation B, installation B will then have the same syncing percentage as installation A. This is usually far faster than doing the normal initial sync over again.

However, when you copy someone's database in this way, you are trusting them absolutely.Bitcoin Core treats its block database files as 100% accurate and trustworthy, whereas during the normal initial sync it treats each block offered by a peer as invalid until proven otherwise.If an attacker is able to modify your block database files, then they can do all sorts of evil things which could cause you to lose bitcoins.Therefore, you should only copy block databases from Bitcoin installations under your personal control, and only over a secure connection.Each node has a unique block database, and all of the files are highly connected.So if you copy just a few files from one installation's "blocks" or "chainstate" directories into another installation, this will almost certainly cause the second node to crash or get stuck at some random point in the future.If you want to copy a block database from one installation to another, you have to delete the old database and copy all of the files at once.