user4529: I am writing transaction monitoring service but I am having some problems with listing since block hash. I have bitcoind daemon and when I execute listTransactions some transactions have same block hash so if I would try to listSinceBlock I would have problems. How this all works?

user1307: The block hash identifies a block. A block can contain multiple transactions, so listsinceblock lists all transactions in blocks newer than the given block hash.
So f.e., if you have this block structure:
block 5 hash: qwertyyuiop
|   tx100,tx101,tx102,tx103
v
block 6 hash: asdfghjklkl
|   tx104,tx105,tx106,tx107,tx108
v
block 7 hash: zxcvbnmnbvc
    tx109,tx110,tx111

When you would do listsinceblock qwertyyuiop, you would get all transactions in blocks older than block 5, so tx104 all the way up to tx111.

4529: <p>I am writing transaction monitoring service but I am having some problems with listing since block hash. I have bitcoind daemon and when I execute listTransactions some transactions have same block hash so if I would try to listSinceBlock I would have problems. How this all works?</p>
 1307: <p>The block hash identifies a block. A block can contain multiple transactions, so <code>listsinceblock</code> lists all transactions in blocks newer than the given block hash.</p>

<p>So f.e., if you have this block structure:</p>

<pre><code>block 5 hash: qwertyyuiop
|   tx100,tx101,tx102,tx103
v
block 6 hash: asdfghjklkl
|   tx104,tx105,tx106,tx107,tx108
v
block 7 hash: zxcvbnmnbvc
    tx109,tx110,tx111
</code></pre>

<p>When you would do <code>listsinceblock qwertyyuiop</code>, you would get all transactions in blocks older than block 5, so <code>tx104</code> all the way up to <code>tx111</code>.</p>
