Block
#18186687
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
892 days ago (Sep-21-2023 08:39:47 PM +UTC)
Transactions:
143 transactions and 96 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.081876493351831832 ETH (0 + 0.461960901020434078 - 0.380084407668602246)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
80,204 bytes
Gas Used:
14,297,042 (47.70%)
Gas Limit:
29,970,676
Base Fee Per Gas:
0.000000026584828363 ETH (26.584828363 Gwei)
Burnt Fees:
🔥 0.380084407668602246 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$1,584.04 / ETH
Hash:
0xda26503ad14206c6bc169029b963b669c0644ccf9220d17fc4504488a2c235c4
StateRoot:
0x49458df1792322518f1f92284ceec12dea5b696241e74d0e6e63662bf0deb52a
WithdrawalsRoot:
0x52241e6c47cfdc0c9ee7229d44dc2d2ceab8d0abd9b50cc9a94ae7cf6cb2b7a7
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x7b378db578f3568a00e0c0d1d637c5687010d1569beaa39d68b53a0aebf66130
Parent Root Hash:
0xe912998c09fa694f75fd92975b11b2b82b14cb27515acd9eb8e6b6e6180e76c1
Beacon Chain Deposit Count:
970786
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x29f3b00ffda9fea18366b8ef27d49d8f9672f5ea4f6aacae74eed3c5527edd4a
Randao Reveal:
0xaa32ed671ff7b1db2194d107fbd515fe2690b2ec65a54412a135b69e7e68a10292333eaec756e73b507432e1a0d86c57121980859cd54266f04e3020a4bc9d9a69ab26f52c34d92e317c28d69955a35aa027c9dc96a93a0bba9a0f5dc364a8bb
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.081262383816646532 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.