Block
#20097683
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
638 days ago ()
Transactions:
132 transactions and 66 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
MEV Builder: 0x563...cf3 in 12 secs
Block Reward:
0.00881364128941525 ETH (0 + 0.088229746906663297 - 0.079416105617248047)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
49,030 bytes
Gas Used:
11,497,221 (38.32%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000006907417507 ETH (6.907417507 Gwei)
Burnt Fees:
🔥 0.079416105617248047 ETH
Extra Data:
ك
�geth�go1.20.14�linux (Hex:0xd983010d0e846765746889676f312e32302e3134856c696e7578)
Ether Price:
$3,566.61 / ETH
Hash:
0x54f49e037aef0405b7f58395c4375200808645542b4ce6ae5d79da69e067c0f1
StateRoot:
0xa2915cd3856df9283f5091526f52a83c4a8f77006ac581e3beb7d0cd1baf506d
WithdrawalsRoot:
0x0166a22d9087713e5f00e67202e5e356818d62f536c7c672d315a4fb462cf863
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x28e6a3132249cd558d47123ef1f77e46aafa05c06ccce02992ca1bf4350f4707
Parent Root Hash:
0x26b24a20a7cd54d17c6e344c451758f80f09bf8fd38cce5229da45780169fdd9
Beacon Chain Deposit Count:
1538543
Slot Graffiti:
Nethermind (Hex:0x4e65746865726d696e6400000000000000000000000000000000000000000000)
Block Randomness:
0x11a0b84766646a337d42ca8613429abc5fcd72d085789bd3a0767325d532f716
Randao Reveal:
0xa0ad5fe2221658d5db4836c55be4ecde5ebd85c0c6ec9ba415dd59e87bba7f94f4f385c406cf3bf7cf7cb33ce1f5958e13d05ffaa8254a40b06a39a7f387d5e44640e9bce2a1a4da557e2768637ca7c05c814d473d561f8550deef97bcdfbd9f
Proposer Fee Recipient:
0x167E7644a25377544d83FF60672C89831bf2Ac0a (MEV Bot: 0x167e...c0a)
MEV Reward:
0.717363582500915936 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
Blob Utilisation:
Blob Gas Price:
Blob Gas Used:
Blob Gas Limit:
Total Blob Fees:
Excess Blob Gas:
Reserve Blob Base Fee:
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.