Block
#21539213
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
431 days ago (Jan-02-2025 08:35:23 PM +UTC)
Transactions:
101 transactions and 52 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.014719862221069241 ETH (0 + 0.102854681358647351 - 0.08813481913757811)
Total Difficulty:
0
Size:
40,920 bytes
Gas Used:
8,767,830 (29.23%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000010052067517 ETH (10.052067517 Gwei)
Burnt Fees:
🔥 0.08813481913757811 ETH
Extra Data:
rsync-builder.xyz (Hex:0x7273796e632d6275696c6465722e78797a)
Ether Price:
$3,452.59 / ETH
Hash:
0xb9687c6078e1a5744dc84b1be774de6f43b17d1c48db9a8259f80a7f77187113
StateRoot:
0x34a1c80c826b5529b6929ed6f8d48e0bf2a4a5d2fceb77c0d050eb51b68529e8
WithdrawalsRoot:
0x1e218278e57ac47fb8dd034af3155c989bf73484495856d011ddc7abb4df9b39
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xa0c9af90e6b5048b569e16e6f754330c74c7175993f7ba2314daefe51d5e00d0
Parent Root Hash:
0x997fab47b6df5840da717f44645f79cffecdfd30b5d439e103b222a1badb9c95
Beacon Chain Deposit Count:
1846271
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x3833f76e02ddec151cff1d9b105a319c4a143888d5e00be8038a779aced9ba07
Randao Reveal:
0x8046fe0001249ac6393fc483e2863d412383f03a9cd7859287e5d1b7c29300ad943c744acd04f8d69c26b194d44e9a41099c7430e743f18035c10fa50bd4ef43f260de90d5b92541235bc9ff57bf3aa3b267d9e6d8c5399d7bced6ae69e3b909
Proposer Fee Recipient:
0xa27CEF8aF2B6575903b676e5644657FAe96F491F (Fee Recipient: 0xa2...91F)
MEV Reward:
0.040208870554021189 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
512 KiB (4 blobs)
Blob Utilisation:
4 Blobs (66.67%)
Blob Gas Price:
0.000000004302552221 ETH (4.302552221 Gwei)
Blob Gas Used:
524,288 (66.67%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.00225577649884365 ETH
Excess Blob Gas:
74,055,680 (565 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.