Block
#20066022
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
624 days ago (Jun-11-2024 03:52:23 AM +UTC)
Transactions:
139 transactions and 69 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.038460346345720186 ETH (0 + 0.142415408961977728 - 0.103955062616257542)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
61,415 bytes
Gas Used:
13,123,599 (43.75%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000007921231258 ETH (7.921231258 Gwei)
Burnt Fees:
š„ 0.103955062616257542 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,497.32 / ETH
Hash:
0x3afd10520d66d25932f8249168b8fadcd1a365dede62ec8202091281e9537bd7
StateRoot:
0xe86b2e5e9ac1c0d6ab8545097aefd5bcaf216aec54366e15efc4a0bafdbf06fe
WithdrawalsRoot:
0x794c58768ec6324aa141c2655d8d66344428f1d5a7709c0c9b15097eeaeba7da
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x38b35a6e1f28d3702ef327946bec5cd422821ba631303a461c788793139ed66f
Parent Root Hash:
0x651ffd5b35a6b68dabcaabb35b7d1f4a573f194f033bfae936f2e814c057f6e1
Beacon Chain Deposit Count:
1527996
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xbbd2f8d536b1f90b9ebfe99e0958d0abae3e5b56aaee993c947dc1f991a47f1c
Randao Reveal:
0x8a469a9bf287396013751031eeff1627685981046ff68b3b28d8f18d6e2a36d4eeea2104a5c1a099e83592db06d45ba7001d58a644a87992781e39dc29a6d63cdf6f1a6ebd3c3caad196e1582d1e2996ccdedde56e75ad4ea961ecbf519d02af
Proposer Fee Recipient:
0x4675C7e5BaAFBFFbca748158bEcBA61ef3b0a263 (Coinbase: MEV Builder)
MEV Reward:
0.070546615523375828 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6 Blobs (100.00%)
Blob Gas Price:
11 wei (0.000000011 Gwei)
Blob Gas Used:
786,432 (100.00%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000008650752 ETH
Excess Blob Gas:
8,126,464 (62 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.