Block
#0xb70500ca8db50a8980f3ee0abad7edb18a8d4c3cab4c8c9aa003ed1e43c33029
Status:
Finalized
Timestamp:
382 days ago (Jan-17-2024 03:29:47 PM +UTC)
Transactions:
173 transactions and 54 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
MEV Builder: 0xDcc...623 in 12 secs
Block Reward:
0.051768422619035184 ETH (0 + 0.72381651972963814 - 0.672048097110602956)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
67,421 bytes
Gas Used:
15,321,469 (51.07%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000043863163324 ETH (43.863163324 Gwei)
Burnt Fees:
š„ 0.672048097110602956 ETH
Extra Data:
rpc.tbuilder.xyz (Hex:0x7270632e746275696c6465722e78797a)
Ether Price:
$2,528.09 / ETH
Hash:
0xb70500ca8db50a8980f3ee0abad7edb18a8d4c3cab4c8c9aa003ed1e43c33029
StateRoot:
0xd0e2cf3771735f8d27ff25d95fd865ae60d771a54668708f313bd1d8a1173db5
WithdrawalsRoot:
0xd7952aec5f03cadf7a8ad3c2651fc027955d2a6e601220184a796df4b85dfaf1
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xba198b7774696cdd296f2c2c83ac0399aa5353d931a7e97beedcc6f68ef74005
Parent Root Hash:
0xb322fe05313873e4d2b7a87e300c32487aeebac8345d4e12ed5b9328398b289b
Beacon Chain Deposit Count:
1173458
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x2add44e2b50e561db6485988f31a08f9156546a3010ef6c375fb0bf86999d450
Randao Reveal:
0xa1dd6a3bf1c2acfafa95ccec2d2e82148ecea5a115522a7f3e028207f4e55a0928ae5293f8620b059c97c6d016c0da2d1319d000a60ea512b2d150066886380ffa564ff99529cbc609f3e135edb1c0783e79bc6db3baded7109596e30a4389ae
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.079490431248421308 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
Blob Utilisation:
Blob Gas Price:
Blob Gas Used:
Blob Gas Limit:
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.