Block
#20000058
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
634 days ago (Jun-01-2024 10:48:23 PM +UTC)
Transactions:
185 transactions and 119 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.028662543479283396 ETH (0 + 0.12861410912159492 - 0.099951565642311524)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
108,792 bytes
Gas Used:
20,136,637 (67.12%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000004963667252 ETH (4.963667252 Gwei)
Burnt Fees:
🔥 0.099951565642311524 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,812.81 / ETH
Hash:
0xee0c4fe96accc4d94ef6a484156fbb310c25346d4ff565ffa1980e448337e57d
StateRoot:
0x8b2d2cc2a0dddc34e2f15ee44306865ac270c58d4c3469973872e52d20006140
WithdrawalsRoot:
0x163e98d73cea21d9453bf2ab22e0307d60afb76c8d6a7033752a12aaa36906f4
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xb31de1928e4c00c611cdc4a5a7f81367a8d9a8add5da17daf96dee0e45725b6b
Parent Root Hash:
0x732b116174bf820e6a2e689858e3aa48e67ff1c413eeae4ed07bb6d25cf76e00
Beacon Chain Deposit Count:
1506233
Slot Graffiti:
TKcdcb1773GEab48ba42 (Hex:0x544b636463623137373347456162343862613432000000000000000000000000)
Block Randomness:
0x26e6cbcf1942c40bc162612164ad815917ce29207093e07e9e6c734f19f87ae2
Randao Reveal:
0xa0ff35791e65b1d4d78fc55aa19b824eade00d0d40dde549e5cc6696c416aceb2c2a907126f0b2f495b74570d63d33f70b2a59708132fc1ff369cc5263c267597ac7e0f0d2bd4c35eb254cd7e5e9b07bfd566ddb6db5308d760a9131bf418630
Proposer Fee Recipient:
MEV Reward:
0.032109835691257524 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
384 KiB (3 blobs)
Blob Utilisation:
3 Blobs (50.00%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
393,216 (50.00%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000393216 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.