Skip to content

Live blockchain

Bitcoin976,778 confirmations

Block 169

Hash000000002a22cfee1f2c846adbd12b3e183d4f97683f85dad08a79780a84bd55

Block 169 of the Bitcoin blockchain was mined on Jan 12, 2009, 03:22:03 UTC. It contains 1 transaction with a total output of 50.00000000 BTC. The miner received 50.00000000 BTC: 50.00000000 BTC of new coins and 0.00000000 BTC in fees. It has 976,778 confirmations.

Transactions

1

 

Size

215 B

 

Total fees

0.00000000 BTC

 

Confirmations

976,778

 

Details

Height
169
Time
Confirmations
976,778
Transactions
1
Total output
50.00000000 BTC
Total fees
0.00000000 BTC
Block reward
50.00000000 BTC50.00000000 BTC new coins + 0.00000000 BTC fees
Size
215 B (215 bytes)
Weight
860 WU
Difficulty
1
Nonce
3718213931
Bits
1d00ffff
Version
0x00000001
Merkle root
d7b9a9da6bec…5e0a87b92d98

Transactions1

#TransactionOutputFee
1d7b9a9da6b…87b92d98Coinbase50.00000000 BTC—
Raw data (JSON)Show
{
  "hash": "000000002a22cfee1f2c846adbd12b3e183d4f97683f85dad08a79780a84bd55",
  "height": 169,
  "txSize": 1,
  "nTx": 1,
  "size": "0.00",
  "fee": 0,
  "totalSum": "50.00000000",
  "difficulty": 1,
  "nonce": 3718213931,
  "bits": "1d00ffff",
  "confirmations": 976778,
  "weight": 860,
  "strippedsize": 215,
  "version": 1,
  "versionHex": "00000001",
  "merkleroot": "d7b9a9da6becbf47494c27e913241e5a2b85c5cceba4b2f0d8305e0a87b92d98",
  "chainwork": "000000000000000000000000000000000000000000000000000000aa00aa00aa",
  "mediantime": 1231715347,
  "previousblockhash": "00000000567e95797f93675ac23683ae3787b183bb36859c18d9220f3fa66a69",
  "nextblockhash": "00000000d1145790a8694403d4063f323d499e655c83426834d4ce2f8dd4a2ee",
  "tx": [
    {
      "txid": "d7b9a9da6becbf47494c27e913241e5a2b85c5cceba4b2f0d8305e0a87b92d98",
      "hash": "d7b9a9da6becbf47494c27e913241e5a2b85c5cceba4b2f0d8305e0a87b92d98",
      "vin": [
        {
          "coinbase": ""
        }
      ],
      "vout": [
        {
          "value": 50,
          "scriptPubKey": {
            "type": "pubkey"
          }
        }
      ]
    }
  ],
  "time": 1231730523
}
Frequently Asked Questions

A block in Bitcoin is a structure that stores confirmed transactions. Each block contains transaction data, a hash of the previous block, and other technical parameters, forming a continuous chain – a blockchain.

A new block is created by miners who collect unconfirmed transactions, form a block from them, and solve a complex mathematical problem (proof-of-work). Once the problem is solved, the block is added to the blockchain and becomes part of the network.

The maximum block size in Bitcoin is about 1 megabyte (MB). With the introduction of SegWit (separated certificates), an effective size of up to 4 megabytes is possible, but the base limit remains 1 MB.

A block contains: a list of transactions, a hash of the previous block, a timestamp, a nonce (a number found by the miner), the network difficulty, and a Merkle hash that combines all transactions into one structure.

Blocks are the basis for storing and confirming all transactions in the network. They form a blockchain - a distributed database that ensures the security and transparency of the entire system.

A block hash is a unique cryptographic 'fingerprint' created by the SHA-256 algorithm. It identifies a block and links it to the previous one (via the hash of the parent block).

The block header is the part of the block that contains key information: the hash of the previous block, the Merkle hash, the timestamp, the difficulty, the nonce, and the version. It is the header that is involved in the mining process.

On average, a new block appears every 10 minutes. This time is adjusted automatically: if miners find blocks too quickly, the network increases the difficulty; if slowly, it decreases it.

Block time is the period between the creation of two consecutive blocks. In the Bitcoin network, it is on average 10 minutes, but can vary due to the probabilistic nature of mining.

The block size determines how many transactions can be included in one block. The size limit affects network throughput and fees: when there is congestion, users are forced to pay more to have their transactions processed faster.