Skip to content
Python-based tools for the Bitcoin cryptocurrency system
Find file
Failed to load latest commit information.
.gitignore Added .gitignore. Better wallet transaction dumping
LICENSE.txt Initial upload to Google Code
NOTES.txt Add support for ckeys (enCrypted keys).
README.txt Link to jackjack-jj's fork of pywallet Fix for tx deserialization. And some fixwallet hacks. Major refactor: make parsing separate from printing. And new tool: fi… b58encode: speedup. Add --check-block-index function to look for block chain prev/next in… Un-hardcode blk0001.dat (main chain is >2GB now) remove dead 'owner' code Un-hardcode blk0001.dat (main chain is >2GB now) Add option to print in JSON format when dumping a block, so output of… Avoid exception on invalid script. Initial upload to Google Code Add more options to fixwallet, allowing partial recovery. New tool Un-hardcode blk0001.dat (main chain is >2GB now) Un-hardcode blk0001.dat (main chain is >2GB now) Remove pdb debugging Major refactor: make parsing separate from printing. And new tool: fi… bsddb is not always needed nor available Be a bit more forgiving on errors.



These tools are becoming obsolete as we move away from using Berkeley DB in

If you are looking for a tool to manipulate the wallet.dat file, you might
want to try


You must run Bitcoin-Qt/bitcoind versions 0.6.0 through 0.7.* with the "-detachdb" option
or these tools will be unable to read the Berkeley DB files.

Now that the bitcoin blockchain is more than 2GB big, some of these tools will no longer
run on 32-bit systems!

Running on a 32-bit system will result in a 'Cannot allocate memory' error when the tools
try to mmap the second blk000?.dat file.

----- -----
Run --help    for usage.  Database files are opened read-only, but
you might want to backup your Bitcoin wallet.dat file just in case.

You must quit Bitcoin before reading the transactions, blocks, or address database files.


Print out  wallet keys and transactions: --wallet --wallet-tx

Print out the "genesis block" (the very first block in the proof-of-work block chain): --block=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f

Print out one of the transactions from my wallet: --transaction=c6e1bf883bceef0aa05113e189982055d9ba7212ddfc879798616a0d0828c98c --transaction=c6e1...c98c

Print out all 'received' transactions that aren't yet spent: --wallet-tx-filter='fromMe:False.*spent:False'

Print out all blocks involving transactions to the Bitcoin Faucet: --search-blocks=15VjRaDX9zpbA8LVnbrCAFzrVzN7ixHNsC

There's a special search term to look for non-standard transactions: --search-blocks=NONSTANDARD_CSCRIPTS

----- -----
Scan all the transactions in the block chain and dump out a .csv file that shows transaction volume per month.

----- -----
Half-baked utility that reads a wallet.dat and writes out a new wallet.dat.

Only half-baked because to be really useful I'd have to write serialize routines to re-pack data after modifying it...

----- -----
Read JSON list-of-objects from standard input, writes CSV file to standard output.
Useful for converting bitcoind's listtransactions output to CSV that can be
imported into a spreadsheet.
Something went wrong with that request. Please try again.