Block
#18544313
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
835 days ago (Nov-10-2023 09:45:23 PM +UTC)
Transactions:
156 transactions and 43 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.034159607545145871 ETH (0 + 0.562113403927560077 - 0.527953796382414206)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
148,754 bytes
Gas Used:
13,462,442 (44.87%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000039216792643 ETH (39.216792643 Gwei)
Burnt Fees:
š„ 0.527953796382414206 ETH
Extra Data:
rsync-builder.xyz (Hex:0x7273796e632d6275696c6465722e78797a)
Ether Price:
$2,078.52 / ETH
Hash:
0xd0082bab207f62850bfa4a74816b81255c31d537706fea816b7f262c27342a0b
StateRoot:
0xd9af0cae604617155cf3802a464610ed2be26459f909b9fe994ab16073007abe
WithdrawalsRoot:
0xd22fd961be4fad0e9ad4f3f48460ccb87e8d1281006cd138a89db51c8fbfd7be
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x4360e971e828ff7208b2723c51e8079b953cc1028e5b4a7755247d536616a7a4
Parent Root Hash:
0xb868e368353ac5cc230528c59891739b41dcd1083d811e225f9137f63030801b
Beacon Chain Deposit Count:
1052639
Slot Graffiti:
Block by Stakely Lido002 (Hex:0x426c6f636b206279205374616b656c79204c69646f3030320000000000000000)
Block Randomness:
0x3ad95366cb718945b7ccdd710f934117917edde7d9fc75f816e7385aec878c2e
Randao Reveal:
0x8c5ca3ea04ac6d1dec5a32daa5e009f7e89031a90600e4d5544b9874b5dba22b7a37fcefe4b8d83861b0def22144394b11640f0cfd27a2151c7e49297e437bdbc9e3d1bdb7fd937286acf2f5715dc13bd458308455034eca6193e2fa2b2bce1d
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.033292485043016498 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.