Hmm, interesting. I've been doing it (very slowly) the naiive way, by querying everything through RPC calls to the Bitcoin Core client. Should be done by next month if I'm lucky. 
Based on the github page for chainstate, the bulk of the output format would be: ;;
Is this correct? If not, please post a small sample of the output.
Based on the github page for chainstate, the bulk of the output format would be: ;;
Is this correct? If not, please post a small sample of the output.
Yeah, that's probably what i will do as next step. I found 'bitcoin-abe' over on git which should be able to read blkNNNN.dat files natively and put them into a SQL db for use as blockchain explorer like thing. But sadly the code is somewhat old, won't run on python3 and .. yeah, overall, it's old..
( you can find it here: https://github.com/bitcoin-abe/bitcoin-abe or using 'pip install abe')My "problem" with bitcoin-abe is, it wants to run directly on the blockchain .dat files, which means, i should shut down my bitcoin knots node as long as abe is running on the files .... or "just copy the whole blockchain over to somewhere else" .. mhmm
I'm not happy doing that anyways, so .. yeah ... connecting the bitcoind and reading anything i want over the RPC thing might be not really fast but more convenient to me.
The sample of the output is in the posting above this one.
Have fun,
hacky