Block
#0x77ca52b3d6ad491b2f544646377d21b0c832a22710455b6a3a977559edf0ffd5
[ This is a Holesky Testnet block only ]
Status:
Finalized
Timestamp:
191 days ago (Sep-17-2024 07:53:36 PM +UTC)
Proposed On:
Block proposed on slot 2558368, epoch 79949
Transactions:
18 transactions and 8 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
0x65Fdc9a172746d54a5B05e6Ac5130b991abAF079 in 12 secs
Block Reward:
0.002204355876626918 ETH (0 + 0.002204355899286918 - 0.00000000002266)
Total Difficulty:
1
Size:
61,920 bytes
Gas Used:
2,832,500 (9.44%)
Gas Limit:
30,000,000
Base Fee Per Gas:
8 wei (0.000000008 Gwei)
Burnt Fees:
🔥 0.00000000002266 ETH
Extra Data:
�geth�go1.22.5�linux (Hex:0xd883010e07846765746888676f312e32322e35856c696e7578)
Hash:
0x77ca52b3d6ad491b2f544646377d21b0c832a22710455b6a3a977559edf0ffd5
StateRoot:
0x639b06d0d3ffc6066316902b07b379b40efd2d3dfd14ec928148be5df235b235
WithdrawalsRoot:
0x2870bf0dfc64e28ecbd34079241368d9320b09ffae81313ca2812679f5321052
Nonce:
0x0000000000000000
Slot:
2558368
Epoch:
79949
Proposer Index:
775368
Slot Root Hash:
0xdfb3b7c5f3f6da9ee3139ef1ef338795da7cdad0ff4870a1d4661ff980d68064
Parent Root Hash:
0xfbb8c6ee47b51774e10cde7794ea4b50293cfd61f6a879a2b3a8a63c44121f63
Beacon Chain Deposit Count:
377408
Slot Graffiti:
GE0xaaLSa728 (Hex:0x4745307861614c53613732380000000000000000000000000000000000000000)
Block Randomness:
0x8c5c19217d2695df7468b6d2851bfcb9188dc5077c6531228bd1608b2ba6f77f
Randao Reveal:
0xb0dd3f2d22f514b25b0cc8ed9ed5c1d435c1a98baa67dd0942e269b40cd92539a33af2fa5b5b73a4c8024410c91a64df0c3fcd2c5b7387b1c29a12c1728144ea5e442d0ff7958cf8df26c54427bf4337d312686852a714ac5018b8ba387a4d4b
:
:
:
Blob Tx:
Blob Size:
512 KiB (4 blobs)
Blob Utilisation:
4.00 Blobs (66.67%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
524,288 (66.67%)
Blob Gas Limit:
786,432
Blocks are batches of transactions linked via cryptographic hashes. Any tampering of a block would invalidate all following blocks as all subsequent hashes would change. Learn more about this page in our Knowledge Base.