Block
#20231479
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
600 days ago (Jul-04-2024 06:52:23 AM +UTC)
Transactions:
112 transactions and 50 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.015125948415975803 ETH (0 + 0.048674353579457331 - 0.033548405163481528)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
55,998 bytes
Gas Used:
10,446,116 (34.82%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000003211567358 ETH (3.211567358 Gwei)
Burnt Fees:
š„ 0.033548405163481528 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,058.81 / ETH
Hash:
0x60a6986dfcd195750679173f4fcd3720bc0c58d0bb04201413a75a2d5534f11c
StateRoot:
0x75616e3ff28920afb41986416fb69d6f82902190b4608aec99014830e076c81b
WithdrawalsRoot:
0x79a62e97a5b7448c10c9682b317baf8a23525f8bd859fb9281dcf1e160b7895e
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x89182ea7b9e36da6a6dd06d72b3eeb3b692bd49e3d23933e05814a98c31cfb08
Parent Root Hash:
0xcefb8584314912b1abfaf49f4841dad92f00ab95fe6180cdebdb2de0039891d1
Beacon Chain Deposit Count:
1569344
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x2c80f6af4fc85bc02f70731e8c4035107655ebafed4763624bd11eec32f1a942
Randao Reveal:
0x89f791b332a447a1998627b6e6e59d199b0c15187a8f8293a74fde87c86581b49967a2a470c45f85e110f2bc858e6cd5077844c08b1c91a77e054cf525a767bf9bc342663e70da9d91d456dc877156b4cad9cbefae2b6cd86d805269b123fa08
Proposer Fee Recipient:
0xCaC200B4E67102B99f8C41189c895D04736C9dD7 (Fee Recipient: 0xcac2...dd7)
MEV Reward:
0.030206598485442273 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
384 KiB (3 blobs)
Blob Utilisation:
3 Blobs (50.00%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
393,216 (50.00%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000393216 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.