user63500: After update Bitcoin Core to version 0.15, chainstate database changed format of data. 
Old prefix of key has been 0x63, now 0x43, and key/value are different
Where is the new format described, or can someone have work on this?
UPDATED
Sample
Key:
43000000dcf3713a29f3da53dbde07ea93ace52a4393ba9a009d8ac17c853c18e500

Value:
d42ade0dfd6a93b6ecbc6098336feedaa21b79128e29d5b7ee2d42


Prefix BYTE:
0x43

TransactionId:
e5183c857cc18a9d009aba93432ae5ac93ea07dedb53daf3293a71f3dc000000

Index VARINT:
0x00 -> 0x00(0)


Code VARINT:
0xD42A -> 0x2AAA(10922)


Block Height:
Code >> 1 = 0x1555(5461)

Is Coinbase:
Code & 1 = 0x00(0)


Value VARINT:
0xDE0D -> 0x2F8D(12173) -> decompressMSB128 -> 0x21084(135300)

Type VARINT:
0xFD6A -> 0x3F6A(16234)


user30668: Each entry in the new 0.15 format is defined as outpoint:coin, and has the following structure:
Outpoint is formed by: key | tx_hash | index.
Where the key corresponds to b'C', or 43 in hex. The transaction hash in encoded in Little endian, and the index
    is a base128 varint. The corresponding Bitcoin Core source code can be found here.
On the other hand, a coin is formed by: code | value | out_type | script.
Where code encodes the block height and whether the transaction is coinbase or not, as 2*height + coinbase, the value is a txout compressed base128 varint, the out_type is also a base128 varint, and the script is the remaining data. The corresponding Bitcoin Core source code can be found here.
Version 0.15 still used an obfuscation key to avoid triggering anti-virus software, you can check this answer to know how it is stored in the database and how to use it to de-obfuscate you data.
Finally, if you need a decoder for both versions 0.14 (0.8-0.14) and the new 0.15 format, you can check this GitHub repo (particularly functions decode_utxo and decode_utxo_v08_v014 from utils.py).
Disclaimer: I'm the author of the repo.

63500: <p>After update Bitcoin Core to version 0.15, chainstate database changed format of data. </p>

<p>Old prefix of key has been <strong>0x63</strong>, now <strong>0x43</strong>, and key/value are different</p>

<p>Where is the new format described, or can someone have work on this?</p>

<p><em>UPDATED</em></p>

<p><strong>Sample</strong></p>

<p>Key:</p>

<pre><code>43000000dcf3713a29f3da53dbde07ea93ace52a4393ba9a009d8ac17c853c18e500
</code></pre>

<p>Value:</p>

<pre><code>d42ade0dfd6a93b6ecbc6098336feedaa21b79128e29d5b7ee2d42
</code></pre>

<hr>

<p>Prefix BYTE:</p>

<pre><code>0x43
</code></pre>

<p>TransactionId:</p>

<pre><code>e5183c857cc18a9d009aba93432ae5ac93ea07dedb53daf3293a71f3dc000000
</code></pre>

<p>Index VARINT:</p>

<pre><code>0x00 -&gt; 0x00(0)
</code></pre>

<hr>

<p>Code VARINT:</p>

<pre><code>0xD42A -&gt; 0x2AAA(10922)
</code></pre>

<hr>

<p>Block Height:</p>

<pre><code>Code &gt;&gt; 1 = 0x1555(5461)
</code></pre>

<p>Is Coinbase:</p>

<pre><code>Code &amp; 1 = 0x00(0)
</code></pre>

<hr>

<p>Value VARINT:</p>

<pre><code>0xDE0D -&gt; 0x2F8D(12173) -&gt; decompressMSB128 -&gt; 0x21084(135300)
</code></pre>

<p>Type VARINT:</p>

<pre><code>0xFD6A -&gt; 0x3F6A(16234)
</code></pre>
 30668: <p>Each entry in the new 0.15 format is defined as <code>outpoint:coin</code>, and has the following structure:</p>

<p><strong>Outpoint</strong> is formed by: <code>key | tx_hash | index</code>.</p>

<p>Where the <code>key</code> corresponds to <code>b'C'</code>, or <code>43</code> in hex. The <code>transaction hash</code> in encoded in Little endian, and the <code>index</code>
    is a <code>base128 varint</code>. The corresponding Bitcoin Core source code can be found <a href="https://github.com/bitcoin/bitcoin/blob/ea729d55b4dbd17a53ced474a8457d4759cfb5a5/src/txdb.cpp#L40-L53" rel="nofollow noreferrer">here</a>.</p>

<p>On the other hand, a <strong>coin</strong> is formed by: <code>code | value | out_type | script</code>.</p>

<p>Where <code>code</code> encodes the block height and whether the transaction is coinbase or not, as <code>2*height + coinbase</code>, the <code>value</code> is a <code>txout compressed base128 varint</code>, the <code>out_type</code> is also a <code>base128 varint</code>, and the <code>script</code> is the remaining data. The corresponding Bitcoin Core source code can be found <a href="https://github.com/bitcoin/bitcoin/blob/6c4fecfaf7beefad0d1c3f8520bf50bb515a0716/src/coins.h#L58-L64" rel="nofollow noreferrer">here</a>.</p>

<p>Version 0.15 still used an obfuscation key to avoid triggering anti-virus software, you can check <a href="https://bitcoin.stackexchange.com/a/52167/30668">this answer</a> to know how it is stored in the database and how to use it to de-obfuscate you data.</p>

<p>Finally, if you need a decoder for both versions 0.14 (0.8-0.14) and the new 0.15 format, you can check this <a href="https://github.com/sr-gi/bitcoin_tools/tree/dev" rel="nofollow noreferrer">GitHub repo</a> (particularly functions <code>decode_utxo</code> and <code>decode_utxo_v08_v014</code> from <a href="https://github.com/sr-gi/bitcoin_tools/blob/dev/bitcoin_tools/analysis/status/utils.py" rel="nofollow noreferrer">utils.py</a>).</p>

<p>Disclaimer: I'm the author of the repo.</p>
