Block
#18128993
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
896 days ago (Sep-13-2023 05:53:35 PM +UTC)
Transactions:
139 transactions and 51 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.017858680725894021 ETH (0 + 0.212621350029915321 - 0.1947626693040213)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
141,962 bytes
Gas Used:
12,407,740 (41.36%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000015696868995 ETH (15.696868995 Gwei)
Burnt Fees:
š„ 0.1947626693040213 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$1,607.99 / ETH
Hash:
0x95d3e3ac2a1f51f2c8cc9e3594c48a4de1941f7599f27e6cc3d7f21559f45277
StateRoot:
0x6e11ace6b0fe97d61da98dc2132bc01512fca7df6555fc9cf486c30bc894377a
WithdrawalsRoot:
0x3935f059989c5891533281abe3a4bb51eb5e1c2d53f94a3898b7014278ef8bbc
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xa19a6d13d49d303ab720658feafa72bbe227562ce1daba1d5484255f6c7ec64f
Parent Root Hash:
0xbdbb9ab5a8811c9d61c7ef71d1f44b0a12efff08589d3668eb2f18d1787717ab
Beacon Chain Deposit Count:
956187
Slot Graffiti:
prylabs-lido (Hex:0x7072796c6162732d6c69646f0000000000000000000000000000000000000000)
Block Randomness:
0x80b9fd0645e386b341f8a77456137ef293e2713ef92bd799f41d372a60c33574
Randao Reveal:
0x8285d94f99d3a321741d6a4a51c489e27ee0ac1a7c6bba7b89c2c108238490c0de4224025a14f264c0e4a2f1f264ab9319b214bdce0e1373189de4b92061fd8666c083fcdcf8d8c424be3109a6fa4e3c553f2e5d3b2cc104b06adb15dce519ba
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.021566099178175825 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.