Block
#20255106
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
597 days ago (Jul-07-2024 02:03:23 PM +UTC)
Transactions:
148 transactions and 63 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.03853693178161353 ETH (0 + 0.084608897970377738 - 0.046071966188764208)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
62,998 bytes
Gas Used:
16,596,272 (55.32%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000002776043089 ETH (2.776043089 Gwei)
Burnt Fees:
š„ 0.046071966188764208 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$2,931.20 / ETH
Hash:
0xd809b6d42ae30249dc3b33717b566e079b79544e3970ec684244424f877e3898
StateRoot:
0xa592af93c37ffbaad3a1be844c1522c1ec689d9ac8c488202ee46e97e93451b4
WithdrawalsRoot:
0x04a857724155e286b5b9828210d9b215a3138d55dece2fb5042d0b1cec534f0f
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xadac66fee753c6a7c9dff338c69e8b7a7f192a3232a8bef0ce9be656c43864bc
Parent Root Hash:
0x03992ee3511957cf1fa4c482c9b5c23cb5e35f18af399be320e295d95b60f246
Beacon Chain Deposit Count:
1573857
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x97114936968e0791014e30804f5e6ac1b401732c07dc2ea90fddda39917ba8d0
Randao Reveal:
0x8c96bd65e10b0c82593450b37ceffe61fbac564973edd6f2b095b759f27ccde428719bb822349eac9099d24d8c5277410f02f9cd50ea03dde365bbd938d1aee9dd3177c64930e9e962c7f15ed404369fb8a8773fbf77f5171339d954b9662923
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.051780240088639369 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
640 KiB (5 blobs)
Blob Utilisation:
5 Blobs (83.33%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
655,360 (83.33%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.00000000000065536 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.