Block
#20410516
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
574 days ago (Jul-29-2024 06:46:47 AM +UTC)
Transactions:
157 transactions and 55 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.034659261828753837 ETH (0 + 0.051788586707305047 - 0.01712932487855121)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
60,818 bytes
Gas Used:
11,795,610 (39.32%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000001452177961 ETH (1.452177961 Gwei)
Burnt Fees:
š„ 0.01712932487855121 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,317.94 / ETH
Hash:
0x1eb3b4a9b16341b6d6a16bc433801936f4c14739f4fa0e686b866731812c55cc
StateRoot:
0x60a169d3abfa12859e105ea2ae8511cb44e7c468b8229c901bad2e5e4b24c8f5
WithdrawalsRoot:
0xb2ef2fb580e31f64fce8a564e78d97ea86001d78ecaf3370ba11c777706c0fae
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x2a303c4cd9b547a89459c918a58633b3a4ec4dd62207334c6c8ffdd5aaf3d1e0
Parent Root Hash:
0xe0acb838652f0cd4a0fe330318f703ac6708389d8b31b0bc25b39d8d0fad16d0
Beacon Chain Deposit Count:
1613826
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x6764fe767cd2637bee7bacb82d6f6cd34902a59b938d02f11c7cb9a2ae1aca07
Randao Reveal:
0x8c2dd34de86017c2c2c4eee2a9109d640a8aa435a5145ade37a7560cf897a02541a7ec6f6bed640e0e479854f6c5020f09a0e4b9636a918a6fc9130da35b66f381972353676141b43b2a69083714b11ea6a534b2b06d602f1ba3c9b66f1d995a
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.040576648816014803 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
256 KiB (2 blobs)
Blob Utilisation:
2 Blobs (33.33%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
262,144 (33.33%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000262144 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.