Block
#20877872
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
508 days ago (Oct-02-2024 12:39:35 PM +UTC)
Transactions:
104 transactions and 32 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.174545559269250899 ETH (0 + 0.231121792964837611 - 0.056576233695586712)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
42,152 bytes
Gas Used:
7,857,428 (26.19%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000007200350254 ETH (7.200350254 Gwei)
Burnt Fees:
š„ 0.056576233695586712 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$2,363.64 / ETH
Hash:
0xca24b724ebcc62b660f15131f495794acb5f6c4778393e4f1fe06d001ebe357e
StateRoot:
0x1446938be318ba5191024233b1f717a5fbf4c2e1dc066e09d022c43da4ca90d4
WithdrawalsRoot:
0xffb5b96e32e69435fc1a61f7615aa3518375be39aec74ca6080409a6ea15a589
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xd1deb92469c7ce49555920fd1042595653bac583ce93f6d6e96db8be74c43cff
Parent Root Hash:
0x4ed660c2de55fb505bbe7fcd477a826f84e004ad472a47fcc324b399f763005d
Beacon Chain Deposit Count:
1701317
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x58793a536518ea02d19e031f4f80341f9df09c3c5001292a10b8c2181d3cae77
Randao Reveal:
0x828695ea933035ad1c545223602a6c3818ecf0b1c14e0e6c2b8c7111567c952f1d3c3e01474130fb7ef611858ef8a3ac1057943ce6b67b1dd13d0607cf2a9157713cec7f5a6b2f67bbc59ff00fc1afe079ef2ded5e0f46a1445f47aec085a9db
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.238689126457690464 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
128 KiB (1 blobs)
Blob Utilisation:
1 Blobs (16.67%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
131,072 (16.67%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000131072 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.