Block
#22405783
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
331 days ago ()
Transactions:
138 transactions and 217 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.013748401519155986 ETH (0 + 0.025422239425943756 - 0.01167383790678777)
Total Difficulty:
0
Size:
60,447 bytes
Gas Used:
35,643,279 (99.20%)
Gas Limit:
35,929,622
Base Fee Per Gas:
0.00000000032751863 ETH (0.32751863 Gwei)
Burnt Fees:
š„ 0.01167383790678777 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$1,833.95 / ETH
Hash:
0xee7c720c03234140fe9f5fa37ac4ee06431ffae1367aabf47276c712ee1ce22d
StateRoot:
0x355e27c1c6517622259ed52c7aafb9b753d8e06faa4c97c5ca91e38be1fe6718
WithdrawalsRoot:
0x77edf2169699a1cce91487b5a6046a6fc7144ec63e514a2db9e273eef7b6637a
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xf6eb8f7fc2c0bb7687c79811addd65884c7dded75026450aeeef0c63ddec9054
Parent Root Hash:
0xe6ed9ff293ba1b9e38aab3ab4d086a58394767f69a3ae4793712deb4387b75e8
Beacon Chain Deposit Count:
2038570
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xcdb1c632b4f64b7bbc7cc3e2fce42217a370b0c2d5f1e8dab8dc91f63bb61ca3
Randao Reveal:
0xa1995b217f19b9dfaab5fe51423fc8391d2cd5d981cc46a2ceda56defcb08a94917efb3cf4f8aa058fe6eb96472d7ed512b97269bceaf0401e20dcf7197b1fd140c48d3ab80a9960a587fa1952f9a5f8e691fb7a32d13840185dd67aa604a456
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.012540311062712656 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
128 KiB (1 blobs)
Blob Utilisation:
1 Blobs (16.67%)
Blob Gas Price:
0.000000000141352284 ETH (0.141352284 Gwei)
Blob Gas Used:
131,072 (16.67%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000018527326568448 ETH
Excess Blob Gas:
62,652,416 (478 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.