Block
#19812065
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
631 days ago (May-06-2024 03:54:47 PM +UTC)
Transactions:
196 transactions and 66 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.034871204124319868 ETH (0 + 0.147341451014141756 - 0.112470246889821888)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
114,938 bytes
Gas Used:
17,397,466 (57.99%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000006464748768 ETH (6.464748768 Gwei)
Burnt Fees:
š„ 0.112470246889821888 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,063.19 / ETH
Hash:
0x7047a72ce991c8f956c3151e34e0e844fc93a03c424705619b57cc2940cc3229
StateRoot:
0xb5eb5fc8bffa0879658c5a0ab7a741b60a7dc63fe3ad986539cecf2b14e6f204
WithdrawalsRoot:
0xc1737a3c56f63765cff0e5398a9c5033983296fabf39f4c187d8c2b07207a65f
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x56c88d0907c47c46f578ca7d135e00fc4aa2f9902babb8a89280eef248bcc57a
Parent Root Hash:
0x9548f178a957254c0c15bf63eaf53ff75feecaf493d2472d61daaa85620fec19
Beacon Chain Deposit Count:
1464681
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x31073f839b4fef79d8a4b3be5bfc714c16b04412d015fa086f1c7c686566d26d
Randao Reveal:
0x889680babe61999fc25c9d893f24abd51f72a41a9b53e740938b7a2008c7261c95bfbf4434b429e30c0eb994f10b74a2088b7cbf5ba00c065577d5bdec72c8097ebb5c6a3dff7f5929119ed634c16ff45cb60e7a6cffa6d02a406f90c064e7ce
Proposer Fee Recipient:
0xfB89a9caFa6EDBB75AFEF66eF90f282c6259F449 (Fee Recipient: 0xfb89...449)
MEV Reward:
0.040236598466526852 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
256 KiB (2 blobs)
Blob Utilisation:
2 Blobs (33.33%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
262,144 (33.33%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000262144 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.