Block
#20095279
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
634 days ago (Jun-15-2024 06:02:11 AM +UTC)
Transactions:
147 transactions and 58 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.016386697040108431 ETH (0 + 0.078284062899555311 - 0.06189736585944688)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
81,131 bytes
Gas Used:
14,495,320 (48.32%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000004270162084 ETH (4.270162084 Gwei)
Burnt Fees:
🔥 0.06189736585944688 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,566.61 / ETH
Hash:
0x86e8891a5ae119ab7d2f85a7aa5e665a6a34565fbd5b9fd26880b20461a2beb1
StateRoot:
0x78127f20c98fb18ecb2a9a2d15580d7f634fa2662f3a73c2f65e201e4555b420
WithdrawalsRoot:
0xe739d3c84ce1872b21ddc4377f716b0b4bf8d636faa07c9201ac682755e9a62c
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x02e1a43b8c2d929d1f2724667bbd7035fac4b75a40a8f1855012a915737c6fa3
Parent Root Hash:
0x9f0023fb76d382b2103652b31deed6fe06c61898546b27fda54d5b2a21fadea5
Beacon Chain Deposit Count:
1538028
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x2a1a1db890267b189e6b984d0458ff3988198fbd6277d2cce683ade204bf39f0
Randao Reveal:
0xa8b30254cf54c00b3ddd9d903e72b9f224a679a3a67e99fcdff4e610081acd68c48d0066292ea63724d948b7ab63823a014669ea1d040d7ba3e5154f4546eb5889f01884aecaa7a0e8e20f010df2567768af682939d966dd9c45bab6d85fadac
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.043168682395385122 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6 Blobs (100.00%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
786,432 (100.00%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000786432 ETH
Excess Blob Gas:
0 (0 blobs)
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.