Block
#20262926
Status:
Finalized
Timestamp:
11 days ago (Jul-08-2024 04:16:35 PM +UTC)
Transactions:
149 transactions and 74 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.043278889253774826 ETH (0 + 0.138402618695995266 - 0.09512372944222044)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
65,650 bytes
Gas Used:
14,226,524 (47.42%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.00000000668636481 ETH (6.68636481 Gwei)
Burnt Fees:
š„ 0.09512372944222044 ETH
Extra Data:
rsync-builder.xyz (Hex:0x7273796e632d6275696c6465722e78797a)
Ether Price:
$3,018.49 / ETH
Hash:
0x2600acd12838da3239877965089a49676100c4d132b9b90f64523f6451bb27d2
StateRoot:
0x79474a63fcf556817bf93612aa758cc1effabe0684d547bb6e54b94e2d8a7e3e
WithdrawalsRoot:
0x1bc51824b6f088b96f81f643326e14a85413d42be3c8d568bb35d40cb5a1ddc8
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x2ac39a21e59282162871cf2e83a2b7ee303f777123c924ba278eb4fdee1ae4c3
Parent Root Hash:
0x282b12c656c9b4c1b6973433cde9e995078c7f4aaf984fc30599c62bf1f14826
Beacon Chain Deposit Count:
1574496
Slot Graffiti:
Everstake / Lido (Hex:0x457665727374616b65202f204c69646f00000000000000000000000000000000)
Block Randomness:
0x1810c8ff6e13d0538b172b8fbb32a0e9be894bd76b62183221601dd3cef17701
Randao Reveal:
0xad52624131a52d7237d3254cf158412bc992c1cc123ec391a785c3e635f1cdd4822587a9ef7a4d7f2f2630015b65599807045fbba7917bb30da4c6491a25c0e1fe0eb12d68eff755a26b783c3a3c8a4e6fecf39e8b9c8ad5bfeb217f3b92bd95
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.424309402576654179 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6.00 Blobs (100.00%)
Blob Gas Price:
59 wei (0.000000059 Gwei)
Blob Gas Used:
786,432 (100.00%)
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.