1
00:00:00,000 --> 00:00:04,740
Every 10 minutes, somewhere in the world, a Bitcoin miner finds a new block.

2
00:00:05,220 --> 00:00:07,280
We all know transactions are in those blocks.

3
00:00:07,700 --> 00:00:08,320
But what else?

4
00:00:08,760 --> 00:00:12,420
Today, on this focus episode, I want to focus on exactly that.

5
00:00:12,780 --> 00:00:13,300
HashrateUp.

6
00:00:13,580 --> 00:00:16,900
Hardware sales, advisory, hosting, and site brokerage.

7
00:00:17,320 --> 00:00:21,360
Find new and used ASIC deals through the website and the Telegram channel below.

8
00:00:21,900 --> 00:00:24,040
Make smarter decisions with HashrateUp.

9
00:00:24,580 --> 00:00:27,020
All right, so first up, we have the version number.

10
00:00:27,020 --> 00:00:29,740
You can think of this as a software number.

11
00:00:29,740 --> 00:00:38,040
Essentially, the miner is telling the network which rules this block is following or which version this Bitcoin block was mined under.

12
00:00:38,500 --> 00:00:42,520
Recently, I did an episode with Bob Burnett where we talked about miner signaling.

13
00:00:42,820 --> 00:00:53,300
And this is exactly where miners can signal by switching specific bits in that piece of data, what version they would like to see adopted going forward.

14
00:00:53,620 --> 00:00:56,520
Next up, we have the previous block hash.

15
00:00:56,580 --> 00:00:58,240
We're talking about a blockchain.

16
00:00:58,240 --> 00:01:03,220
chain there needs to be something that links the chain pieces together links the blocks together

17
00:01:03,220 --> 00:01:09,760
this is exactly that the previous block hash is included in the block header of the currently

18
00:01:09,760 --> 00:01:15,820
being mined block to make sure that there is a reference to the last block and it's not possible

19
00:01:15,820 --> 00:01:23,320
to mine the blocks by themselves this chain as we know goes all the way back to block zero and all

20
00:01:23,320 --> 00:01:29,060
previous block hashes are included in every block along the way and so this makes sure that if

21
00:01:29,060 --> 00:01:34,460
somebody wants to change something in the Bitcoin blockchain that they have to start right at the

22
00:01:34,460 --> 00:01:42,680
beginning next up we have the Merkle root you can think of this as a hash that combines all the

23
00:01:42,680 --> 00:01:59,346
transactions in the Bitcoin block so all the transactions get paired up and then hashed until So you reach the Merkle root and that is what is being included in the block header So what that does is that we don have to check every block individually as we go

24
00:01:59,466 --> 00:02:02,586
but we can just check the Merkle root for any changes.

25
00:02:02,586 --> 00:02:06,446
Because if one of the transactions included in this Bitcoin block changes,

26
00:02:06,566 --> 00:02:10,086
even by a single digit, the entire Merkle root will also change.

27
00:02:10,486 --> 00:02:11,366
Why we do this?

28
00:02:11,506 --> 00:02:13,146
We do this for efficiency reasons.

29
00:02:13,146 --> 00:02:20,766
If one of the Bitcoin transactions changes even by a single digit along the way, now the entire Merkle root hash changes as well.

30
00:02:21,046 --> 00:02:29,506
So this makes sure that we only have to check the Merkle root instead of having to check constantly all the Bitcoin transactions that the miner selected for the block.

31
00:02:29,866 --> 00:02:35,726
This is something we can explore in a separate focus episode where we can go into the Merkle root itself.

32
00:02:36,606 --> 00:02:38,666
So next up, we have the timestamp.

33
00:02:38,786 --> 00:02:43,526
This is just to signal to the network the time at which this block was created.

34
00:02:43,806 --> 00:02:51,146
This is also used in difficulty computations to make sure that we're always reaching that 10-minute target.

35
00:02:51,466 --> 00:02:58,446
So if the average difference between the blocks was higher or lower than 10 minutes, the difficulty adjusts accordingly.

36
00:02:59,086 --> 00:03:01,866
So here, the Bitcoin network allows for some flexibility.

37
00:03:01,866 --> 00:03:10,826
The timestamp cannot be more than two hours in the future and has to be after the median of the last 11 blocks.

38
00:03:11,466 --> 00:03:20,626
The rules around the timestamp have to do with a specific attack on the Bitcoin mining network, which is another thing that we can explore in a separate focus episode.

39
00:03:21,426 --> 00:03:24,126
After that, we have the difficulty target.

40
00:03:24,126 --> 00:03:33,706
This is the target that the miner enters here to make sure that it follows the current difficulty target of the network that the nodes around the world agree on.

41
00:03:33,986 --> 00:03:47,092
If this target is set incorrectly the block will not be accepted The lower the target is the more difficult it is to mine Bitcoin blocks the more difficult it is to find Bitcoin blocks and the higher it is the easier it becomes

42
00:03:47,732 --> 00:03:52,612
This difficulty target is derived from the current difficulty, but the difficulty target

43
00:03:52,612 --> 00:03:59,092
and the difficulty themselves are separate things. Last but not least, we have the nonce. This is the

44
00:03:59,092 --> 00:04:05,892
bit of data that gets iterated, meaning this is the data that changes trillions of times a second.

45
00:04:05,892 --> 00:04:17,952
If you own and run a miner with 270 tera hash, an S21 XP, for example, that means that that miner hashes 270 trillion times a second.

46
00:04:17,952 --> 00:04:31,172
And that means it's changing the non-s 270 trillion times a second to arrive at a specific outcome that shows the network that you reached the difficulty target.

47
00:04:31,672 --> 00:04:34,832
BitX, solomining.de got it.

48
00:04:34,832 --> 00:04:41,952
premium made in germany you want to go fancy go for nerdx or nerdqx plus plus for a lot of power

49
00:04:41,952 --> 00:04:47,952
worldwide shipping check out solomining.de today so after what i've just explained i want to go with

50
00:04:47,952 --> 00:04:55,872
you guys to mempool.space to look at a block in more detail right so here we have all the previously

51
00:04:55,872 --> 00:05:01,712
mined blocks you can do this until you reach block zero we're not going to do that it's going to take

52
00:05:01,712 --> 00:05:10,752
a while right so the last block mind was block 940536 and we can see some basic data here right

53
00:05:10,752 --> 00:05:17,872
so we can see the average fees that were paid we can see that it consisted of 1823 transactions

54
00:05:17,872 --> 00:05:24,672
we can see the total fees here and when it was mined so 22 minutes ago if we click on that block

55
00:05:24,672 --> 00:05:41,358
then we can see more details right so we can see what hash won this block right we can copy that and look at it in a separate file It a number that starts with a lot of leading zeros It a hexadecimal number So it includes letters as well

56
00:05:41,358 --> 00:05:47,658
as numbers. We can see the timestamp at which it was mined, right? So 23 minutes ago, you can see

57
00:05:47,658 --> 00:05:53,258
the size, weight, the health, another issue we can get into separately. You can see the fee span here

58
00:05:53,258 --> 00:06:00,778
as well so the lowest fee was one set per vbyte and the highest fee paid was 600 sets 650 sets per

59
00:06:00,778 --> 00:06:09,098
vbyte the median was about one currently fees are very very low so make sure that you clean house

60
00:06:09,098 --> 00:06:18,058
and consolidate your transactions to avoid high fees later total fees paid 0.022 bitcoin subsidy

61
00:06:18,058 --> 00:06:27,018
plus fees so that's 0.022 plus the current subsidy 3.125 bitcoin you can see total fees again and

62
00:06:27,018 --> 00:06:32,298
then down here you have all the transactions right and notably you always have in every block the

63
00:06:32,298 --> 00:06:37,178
first transaction is always the coin based transactions right so this is where bitcoin

64
00:06:37,178 --> 00:06:44,538
enters the world previously held by the network and now dished out every 10 minutes currently 3.125

65
00:06:44,538 --> 00:06:46,098
of Bitcoin being mined.

66
00:06:46,098 --> 00:06:47,778
And that concludes it, right?

67
00:06:47,778 --> 00:06:52,238
So to go back, we have in the block header,

68
00:06:52,238 --> 00:06:55,078
we have the nonce, difficulty target, timestamp,

69
00:06:55,078 --> 00:06:58,378
Merkle root, previous block hash, and the version.

70
00:06:58,378 --> 00:07:01,778
And then the block itself consists of the block header

71
00:07:01,778 --> 00:07:03,658
and the transactions.

72
00:07:03,658 --> 00:07:04,818
So I hope that helped.

73
00:07:04,818 --> 00:07:06,518
Let me know if you have any questions

74
00:07:06,518 --> 00:07:09,618
or if anything remains, leave your comments down below.

75
00:07:09,618 --> 00:07:11,818
I'm sure there is more details to be added

76
00:07:11,818 --> 00:07:14,038
by you knowledgeable folks.

77
00:07:14,038 --> 00:07:16,798
That being said, have a great day and a wonderful week.

78
00:07:16,798 --> 00:07:17,638
See you later.