Block
#17225083
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
1028 days ago (May-09-2023 07:52:59 PM +UTC)
Transactions:
179 transactions and 147 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.898319606373310561 ETH (0 + 3.192716420450201533 - 2.294396814076890972)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
212,313 bytes
Gas Used:
21,535,572 (71.79%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000106539859451 ETH (106.539859451 Gwei)
Burnt Fees:
🔥 2.294396814076890972 ETH
Extra Data:
rsync-builder.xyz (Hex:0x7273796e632d6275696c6465722e78797a)
Ether Price:
$1,849.03 / ETH
Hash:
0x459450f8f9a8d9b56f3badef46e6e00aeb1397a5f6af21645f0d6568c172021b
StateRoot:
0x7a476568ad6e58a1d15fd3516f05e708d5cc20fbe03bd29d1871e611b7783eec
WithdrawalsRoot:
0x93b9cddb69304a2dcf3d815da06df6472a1e9eb63d22fa1f4a5e255b7fa155e3
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x88f2093e60f20441c9ffd5d5c7730770335f2afb681700f4c64f98415f109425
Parent Root Hash:
0xd2ed92daee3ae9f150877b3fcb3c16e17543cb5a83d099fe157d030d993a3a49
Beacon Chain Deposit Count:
666643
Slot Graffiti:
Lodestar-v1.8.0/a4b29cf (Hex:0x4c6f6465737461722d76312e382e302f61346232396366000000000000000000)
Block Randomness:
0x6aaf6fccd1af7bc0fbea6a1cbe6d6dd6da7ffc95fb38c0b21a4905b27120511a
Randao Reveal:
0xa2c1a65332e726da138d0d41a1c9b8607fd95d29cd0b3aa0e5295695b50ac41225813cea8448e06ed02075d32cb1935c0a3f1a27289f2bb1ffa9d25f47faeb867d0afbcb6febc5d0257d117fdb62f5fe268f7e6855664ec241030a1f8b1fd784
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
1.014785824623951916 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
Blob Utilisation:
Blob Gas Price:
Blob Gas Used:
Blob Gas Limit:
Total Blob Fees:
Excess Blob Gas:
Reserve Blob Base Fee:
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.