user59315: I was tracking a transaction using a Bitcoin Core command. I was able to extract info on whether the transaction had entered the mempool.
Among the information I got were details such as "the block height when the transaction entered the mempool".
Does this mean that blocks 'carry' unvalidated/unverified, but unconfirmed, transactions?

user121614: Blocks don't "carry" any unconfirmed transactions. By definition, a transaction is confirmed when it's included in a block.
Importantly, the block height when the transaction entered the mempool might be different from one mempool to another, as transactions take time to propagate through the network and a new block might be mined while it's propagating. It will also be different for transactions that your node receives from its peers when it's starting again after a downtime, since those transactions may have been in their mempool for many blocks already.

59315: <p>I was tracking a transaction using a Bitcoin Core command. I was able to extract info on whether the transaction had entered the mempool.</p>
<p>Among the information I got were details such as &quot;the block height when the transaction entered the mempool&quot;.</p>
<p>Does this mean that blocks 'carry' unvalidated/unverified, but unconfirmed, transactions?</p>
 121614: <p>Blocks don't &quot;carry&quot; any unconfirmed transactions. By definition, a transaction is confirmed when it's included in a block.</p>
<p>Importantly, the block height when the transaction entered the mempool might be different from one mempool to another, as transactions take time to propagate through the network and a new block might be mined while it's propagating. It will also be different for transactions that your node receives from its peers when it's starting again after a downtime, since those transactions may have been in their mempool for many blocks already.</p>
