Quote from: nc50lc on February 26, 2024, 12:14:05 PM

Quote from: promise444c5 on February 26, 2024, 11:44:11 AM

Oops didn't thought it that way ,thanks for the clarity.
However, can you clear me a little bit more on "coinbase transaction" I'm still a little bit confused. Sorry for getting too inquisitive over this topic

That's a general term for the first transaction in the block where the coinbase (or the block reward) is included as input.
Not to be confused with the company with the same name which is usually written with upper-case "C".

You can use any blockexplorer and look for blocks, like block height 800000: blockstream.info/block/00000000000000000002a7c4c1e48d76c5a37902165a270156b7a8d72728a054
The first transaction is the so called coinbase transaction.

Understood!

Quote from: ranochigo on Today at 06:01:13 AM

The nonce is a variable that can be used for the hash to be different; anything that changes the input hash (block header) would change the resultant block hash. Since using the exact same input gets the exact same hash, we would have to ensure that the nonce is different by incrementing it with every iteration. If not, then using the same random nonce and the same block headers could result in recomputing the same hash. Not all of the implementations will add 1 to the nonce, and certain clients may choose to skip nonces but the result should be that the nonce are distinct if the rest of the block headers are the same.

Thanks for this I'm quite learning alot from it, it took me a while to understand as I had to go through it over and over
I have another question: if not all client use the +1 system then how will they get a distinct nonce or could there be a possibility of an input hash not having a nonce