2019-05-13 15:23:14 +00:00
|
|
|
---
|
2021-09-02 08:40:09 +00:00
|
|
|
summary: 'a container of transactions, a sequence of which forms a blockchain'
|
2019-05-13 15:23:14 +00:00
|
|
|
terms: ["block", "blocks"]
|
|
|
|
|
---
|
|
|
|
|
|
2020-08-16 17:11:02 +00:00
|
|
|
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
2021-09-02 08:40:09 +00:00
|
|
|
|
2019-05-13 15:23:14 +00:00
|
|
|
### The Basics
|
|
|
|
|
|
2021-09-02 08:40:09 +00:00
|
|
|
A block is a container of @transactions, with a new block being added to the
|
|
|
|
|
@blockchain once every 2 minutes (see constant `DIFFICULTY_TARGET_V2`
|
|
|
|
|
defined as 120 seconds), on average.
|
2019-05-13 15:23:14 +00:00
|
|
|
|
2021-09-02 08:40:09 +00:00
|
|
|
Blocks also contain a special type of transaction, the
|
|
|
|
|
@coinbase-transaction, which add newly created Monero to the network.
|
2019-05-13 15:23:14 +00:00
|
|
|
|
2021-09-02 08:40:09 +00:00
|
|
|
Blocks are created through the process of @mining, and the @node that
|
|
|
|
|
successfully mines the block then broadcasts it to each of the @nodes
|
|
|
|
|
connected to it, who subsequently re-broadcast the block until the entire
|
|
|
|
|
Monero network has received it.
|
2019-05-13 15:23:14 +00:00
|
|
|
|
2021-09-02 08:40:09 +00:00
|
|
|
Fake or bad blocks generally cannot be created, as @nodes that receive
|
|
|
|
|
blocks always verify the @transactions they contain against a set of
|
|
|
|
|
consensus rules that all nodes adhere to, including validating the
|
|
|
|
|
cryptographic @signatures on each transaction.
|
