Block
#20632088
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
543 days ago (Aug-29-2024 05:14:47 AM +UTC)
Transactions:
88 transactions and 51 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.007460606798843345 ETH (0 + 0.014391930148954169 - 0.006931323350110824)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
38,304 bytes
Gas Used:
7,862,276 (26.21%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000000881592474 ETH (0.881592474 Gwei)
Burnt Fees:
š„ 0.006931323350110824 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$2,527.97 / ETH
Hash:
0xc4df425c3b3af075db5ada8b0e911c800bfae89ca87fe7d16e2a95983f52d49b
StateRoot:
0x625b986880baa1756529e4d1c9cfe7108ce00693c292dded8c885be5bbeedba5
WithdrawalsRoot:
0x7f7aba4ac366c58b89c21bac7a7d99a082092d116b88bb2a3fc39fa9aef26f4f
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x700733177cc457d46bc4b5e59fb9ab3b70cb913adbe40c356bf863fb08631955
Parent Root Hash:
0xa180d5f068e237a98dc90c7c582834937b16350b3039ed3ef19e78e1c7c7daf8
Beacon Chain Deposit Count:
1659447
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xb0bd8c44fd0d05cfadcc1bc485ce4d9f702c1f70da1c5aaf15fb55c74e073e19
Randao Reveal:
0x8f4e13c0c4fb11ee5cc9e2f10bdcf9da0d2169359de264f3a10718fdfd9a3e5ff235c1b8dd7eee55a3847d0bccfd4eed1817d1106848c9015f26e5ff44fdd7302113bbc9c49e4d57fb5b68b3db6b60a2b404e99101a0d61d5aa23dfd947318d8
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.01059899646617391 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.