Block
#20231738
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
571 days ago (Jul-04-2024 07:44:35 AM +UTC)
Transactions:
297 transactions and 103 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.05661474650160081 ETH (0 + 0.14925338272530585 - 0.09263863622370504)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
170,269 bytes
Gas Used:
29,925,840 (99.75%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000003095606881 ETH (3.095606881 Gwei)
Burnt Fees:
š„ 0.09263863622370504 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,058.81 / ETH
Hash:
0xf470d635b5f95fa00dd85d164949af058c6e6c81a77b9041668d2926d1a16ad2
StateRoot:
0x02bba6217e49e5b5c23b74ce583fd3bcfc213d92716b9c80cc0851ff5336644c
WithdrawalsRoot:
0x562bfbe1111d0702068ab58b5330ff0ad7243f72f4419b8e00b8c1aa100c64ba
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xb703fb629f5bb65c55d544911ee72eed52660ef130d0edd8f70dd21af5678778
Parent Root Hash:
0xa5fe65fde0765b88f76e7a2029c9978545ba980ccffc239ee4be1a1469671bf0
Beacon Chain Deposit Count:
1569344
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x09ba7ebef5e20a8887f2b8b0194c2b6c6a6cc50ee37374e0167cfd3c6aee1eb9
Randao Reveal:
0xa68049cd5667eeab8485ad2bfa0c5467e8a9603082e5c5c63f7b9241dbc7c5df7c93e3dd6b7304139c31193a6c55010a059d78d49efe0bad847c644d3ea162a9ea031ecafa0dc33561918ef7c4d6902f98a6dc4170b2a99590317fa0fe4583b1
Proposer Fee Recipient:
0x58cb0D9D6fA1ebd9B4076a59e7D0471322F7bBb3 (Fee Recipient: 0x58...Bb3)
MEV Reward:
0.033502766411257562 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6 Blobs (100.00%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
786,432 (100.00%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000786432 ETH
Excess Blob Gas:
1,835,008 (14 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.