Block
#20258747
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
598 days ago (Jul-08-2024 02:15:35 AM +UTC)
Transactions:
188 transactions and 58 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.051004678522208292 ETH (0 + 0.102355387712160723 - 0.051350709189952431)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
133,888 bytes
Gas Used:
18,593,271 (61.98%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000002761789961 ETH (2.761789961 Gwei)
Burnt Fees:
š„ 0.051350709189952431 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,018.49 / ETH
Hash:
0x7353191097cc90644dcdadae6c8b22c0130139d58af3a5a4d52b88aa1b1ec430
StateRoot:
0xef69b25503d3640872627312d6135d53e05001d4e0a971de2d25aa185d636f8f
WithdrawalsRoot:
0xc03b30c23c462ce4bdf8b1bb050668fdf9034d88334a9299af093d41f7179168
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x2dcd7a96eb2b04499ee552c3bef8cd533c1fb02af745821467035ae894125fb0
Parent Root Hash:
0xfe3fbe988d9abed6ad7da59ad3e0a7e71783426725a16d8ed242145ac8d7af6b
Beacon Chain Deposit Count:
1574068
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xa9779631e43e7f016105d3d8352edb226e7796fa15c3f1260b4ecdebeca7543c
Randao Reveal:
0x8fa57e481a37f981e416af87f022b3a1375d17edc7b1d49e4339b34e8ca90dfd8978f823cb2bc1a6a2295552cab053b115a2230a0e61521cf59b8d61c531ccaf0e9b7f8bb24e2319d10d9958f58f24fed18d7efd512595bfa064a7a2716a4b9d
Proposer Fee Recipient:
0x52f6f20582F9126716e21cb3dB5FAaaC4df8357B (Fee Recipient: 0x52f6...57b)
MEV Reward:
0.067388334984109891 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:
393,216 (3 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.