Block
#20045053
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
617 days ago (Jun-08-2024 05:34:35 AM +UTC)
Transactions:
145 transactions and 41 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.010145538694668578 ETH (0 + 0.063219500288146022 - 0.053073961593477444)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
56,164 bytes
Gas Used:
10,871,067 (36.24%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000004882129932 ETH (4.882129932 Gwei)
Burnt Fees:
🔥 0.053073961593477444 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,680.84 / ETH
Hash:
0x0939dc8b721fd4eff11c8038ea40dccf0dd2f9b03bae9593a80566689b432574
StateRoot:
0xabeb7c587fcfd76c3e7a23f86545d2a455bd8f03ecd476cab3f978c3d90cfd68
WithdrawalsRoot:
0x43fb88057b6f1ab1786841b11c86066de80ce90f44a50506a9b0ce4159adab36
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xd7545321886d6efda7b063f384b8039ba496967dd549a3c411bb0a92e7b272ed
Parent Root Hash:
0xfd098337b34afef62c4575ed9ab2af2f232feeb81d5540fc4e949f10165c233c
Beacon Chain Deposit Count:
1521779
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xb6d688ab6a77ccea7b52c71a8e15703c433e81f0b70d9980d69ffc72b8724ada
Randao Reveal:
0x8b509aef25c4b700a57377d9f4e3e7ff2b4fed95b0aac85f8bb877d54c55bd685b930b52b966e98fcd85c4bf99c11aed15ec99848525c11e17aa0c22e48052a7aab924fa996d7a3668bc2a2edb60fdd4fe320ac4d53f7040844e20c7f32f59d0
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.01446742636722732 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.