Block
#19726377
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
670 days ago (Apr-24-2024 04:19:23 PM +UTC)
Transactions:
170 transactions and 78 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.022912530170970482 ETH (0 + 0.227270100583413042 - 0.20435757041244256)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
72,692 bytes
Gas Used:
14,296,834 (47.66%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.00000001429390384 ETH (14.29390384 Gwei)
Burnt Fees:
š„ 0.20435757041244256 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,139.10 / ETH
Hash:
0x269487c59971ff39b54bc9f0467cf87a95b15ae2bd74cea65b680ddd6d23fd7e
StateRoot:
0x34b892a3220a1640151f0c56cefd6377a7424d632613b034be7b3b449af26172
WithdrawalsRoot:
0x4142511792ab58486cbef8e0ec2f622e9743a4a66e4801e7d5e511598a3e0a67
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xda57408ffc622b11bb5cbb3119bbb6a685037a6038bee44f1f0fefb1eae86440
Parent Root Hash:
0xbbc9dc2d66da185a8425dead6976d0e12c3449002f81d8892f47c8278cd2bad5
Beacon Chain Deposit Count:
1453272
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x6b461a15e09477731896d727fd11260fa236571db0726803325be907f8b9eabb
Randao Reveal:
0xa4237e2ab05cb8f79dec3e57fe0e071ea510883d3eab50385da90b4fbbcf15dce71411335a149314c54469979d60dae70a50ccab03f6799bfa248830695ea6c10295e3799630659c89f005cfe7262415b2bee8c1badf4dd2096d274dd39a6d9d
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.026594175498942711 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:
0 (0 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.