Block
#20161887
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
613 days ago (Jun-24-2024 01:37:59 PM +UTC)
Transactions:
220 transactions and 84 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.032077963492111161 ETH (0 + 0.144675066008816577 - 0.112597102516705416)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
85,284 bytes
Gas Used:
18,175,464 (60.58%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000006195005669 ETH (6.195005669 Gwei)
Burnt Fees:
🔥 0.112597102516705416 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,350.54 / ETH
Hash:
0x4de0027274f4b858eec4d6078c1c144825785065aa73fb10402669b6681fe1b2
StateRoot:
0xefe906c3c3ba2ff9616161d351d2ff81ec2e1af1faffff60fb9805df270711d5
WithdrawalsRoot:
0xf842ce2b715e3cf6b757c9c25b9d96987579a23f38361efe0dfedf82b13e1bd9
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xbfdc7b626c42b9186e6e1e4857a0e9c6afe1ab3f46e917f0bf7390d87cbf66c9
Parent Root Hash:
0x738a5cdd30b295c2e68c1d30784a70013345419013ed031043f3ff28dd143ecf
Beacon Chain Deposit Count:
1555703
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x35c5b0052a793c48960ceab28782e74bb6983ee37fe4da712467f06e62255ca5
Randao Reveal:
0xa4ef3a46af4565d88aab505578c7baca83f4a81de1801b4bbed6214d028fb67f3a3403abf158c93822922f94d540686518b16d1d9dc621794930b695516e772d112aa9f05dfd9cb712f593f1e78907b1bce761d1621508ff835b517d8fef2020
Proposer Fee Recipient:
0xa27CEF8aF2B6575903b676e5644657FAe96F491F (Fee Recipient: 0xa2...91F)
MEV Reward:
0.039872620150349885 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
512 KiB (4 blobs)
Blob Utilisation:
4 Blobs (66.67%)
Blob Gas Price:
35 wei (0.000000035 Gwei)
Blob Gas Used:
524,288 (66.67%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.00000000001835008 ETH
Excess Blob Gas:
11,927,552 (91 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.