Block
#20238413
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
572 days ago (Jul-05-2024 06:07:59 AM +UTC)
Transactions:
172 transactions and 49 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.020380957312237088 ETH (0 + 0.190510281216011116 - 0.170129323903774028)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
67,599 bytes
Gas Used:
13,897,066 (46.32%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000012242103758 ETH (12.242103758 Gwei)
Burnt Fees:
š„ 0.170129323903774028 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$2,982.07 / ETH
Hash:
0xc4a9133197acaa56f0531173235e067f4d8fe70bd0bc2b177cd89f69732a4d06
StateRoot:
0xa409a45a5a86ffac512807d83862e73cd0acc48f35c033f5e839b2fadff3d732
WithdrawalsRoot:
0x0245303f907a6b8f3bbc069d1730978ec00e5eea65863940ed095ac7e6d58538
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x64bd5a719e4f31e34650fa4265480643686d70e18da623aa09cc894561bdf3c7
Parent Root Hash:
0x1ab07cd254af1bdb218cdc0e49c246f4a62a2b90db27343a288355de38e254b0
Beacon Chain Deposit Count:
1571663
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x48c67b8c5f7d645423e7e1d61b261f79d02df2212810f5522ef2d3dfa03a60e6
Randao Reveal:
0xa4839e2194279e06bd3d958127c3ddbaed365c978a691d2eb1d9567f6bedc3f2eaa58101df3a130f30b89bcc2ebc86fc16c6c88fe85b5dc15d8252938b45b65a10e8d32493bd8efe9b20e18971b174fdcd6aa7f1fa7118bf2053558c260a84c6
Proposer Fee Recipient:
0xa95a23115B0aB94182C5893E1A45140F0F3B6D53 (Fee Recipient: 0xa95a...d53)
MEV Reward:
0.038931777767361259 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
512 KiB (4 blobs)
Blob Utilisation:
4 Blobs (66.67%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
524,288 (66.67%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000524288 ETH
Excess Blob Gas:
262,144 (2 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.