Block
#18913632
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
795 days ago (Jan-01-2024 04:00:59 PM +UTC)
Transactions:
145 transactions and 57 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.051071534364383353 ETH (0 + 0.247680383757424899 - 0.196608849393041546)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
154,422 bytes
Gas Used:
15,461,326 (51.54%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000012716169971 ETH (12.716169971 Gwei)
Burnt Fees:
🔥 0.196608849393041546 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,352.65 / ETH
Hash:
0x9aa58ca84b334e0953b5c364f81ea991f5fb13f0d1813b07825fd657c9ce3136
StateRoot:
0xeb1e9444633eb8ef7cc5b8e0d5b3785f1db200e832c993fc21ef7e6fbef5fa0f
WithdrawalsRoot:
0xa418d574954b9c4182e3952841db6dd4df27993ea879cf5f44507e87ba3445ed
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xe5a7f0683e723ae01aeb9676dc6f822bf4d7e551e2cc0f541eab9e233c4147e5
Parent Root Hash:
0xbc220de972ecef05020724acf4e366a1b7a98fe31bead39a348dbb47e447f563
Beacon Chain Deposit Count:
1147121
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x3d9fd37c99db11dfa8c5a1ae680b91cd2cc50455033b52d1ade8405af463a67f
Randao Reveal:
0x84f2a372560e7f510b3e0e7d558078de5fe77e13ca355d7e1d5b3bb295c2ebbd59f80d09c7cb822a71c1df05919f67110394238cf43dc07366b726a5a0bf90bff4d63fea5d9df0a3da70832d52ccba0f0d8ff1d3a6cecbd840768a385080c6ad
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.051190367130154572 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
Blob Utilisation:
Blob Gas Price:
Blob Gas Used:
Blob Gas Limit:
Total Blob Fees:
Excess Blob Gas:
Reserve Blob Base Fee:
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.