Block
#19808689
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
670 days ago (May-06-2024 04:33:47 AM +UTC)
Transactions:
114 transactions and 53 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.012804867902858783 ETH (0 + 0.060559853211781331 - 0.047754985308922548)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
50,072 bytes
Gas Used:
11,391,894 (37.97%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000004192014542 ETH (4.192014542 Gwei)
Burnt Fees:
🔥 0.047754985308922548 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,063.19 / ETH
Hash:
0x5eb70aaeb7db92ad832240e574e4c9a7ff007366eccc4ce1a07d5000572d05d8
StateRoot:
0xf8b68c383ceb1870e69e996ace685922c22e5393e9195e61bb312a52265d6a83
WithdrawalsRoot:
0xb95120f82ed0f4682e1e5a38a13712bef1110226ca79e556c6863b16a1dfbafd
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x5acdaf08eb66f97957f16b57e953368ba25d0e72b1365abc5906fc61b1c5276c
Parent Root Hash:
0xb9ae70035c4e8c73dc013f480773660ff55f1757d2d958a693b9a32d88c0ead4
Beacon Chain Deposit Count:
1464404
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x8a44d5e8dc26f036ff1e0913dc98849d1862abbb13da80d8d52ad203efc346cb
Randao Reveal:
0x938f4f5cc9d14f8f98066e24bcc080f907c1d97a48bb00e16ae5696b896ca86bf578eeff20a3dffacc8062801dd026d516323f66a5451b08048fb461e111721385518453e1955ab6729ecdebfc19db4e53e994730c8805772c13b174e9a8edd6
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.015799162265909815 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
128 KiB (1 blobs)
Blob Utilisation:
1 Blobs (16.67%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
131,072 (16.67%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000131072 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.