Block
#17358490
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
982 days ago (May-28-2023 03:45:23 PM +UTC)
Transactions:
141 transactions and 53 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.299829869863478636 ETH (0 + 0.712258366292530988 - 0.412428496429052352)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
85,027 bytes
Gas Used:
12,636,896 (42.12%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000032636851362 ETH (32.636851362 Gwei)
Burnt Fees:
🔥 0.412428496429052352 ETH
Extra Data:
@builder0x69 (Hex:0x406275696c64657230783639)
Ether Price:
$1,909.21 / ETH
Hash:
0xc13917926808ef556f116be6c0dd75fa9543f28f1fbde572d71d6add2172a65d
StateRoot:
0x9224a9ecfa8153dd49017f061c7f01f13b333b46ac0287a122e121291ca19d9b
WithdrawalsRoot:
0x85deee76ef9ea657da2f3b9b28e7b8e0743c7aa949f26ccc0d60cbad17d94a5c
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xbdf47cddfd0135c2037bcd2ce079006778a6e015d5acd38173b0483b17e53cd9
Parent Root Hash:
0x087751b5aa395970f2a5f59f9e5b6e0236d875e7cd39edbf6453528e45b531c7
Beacon Chain Deposit Count:
748547
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x85fe739b71593883cecf1b3d27be285b934bae533905734bd2499704ef898da2
Randao Reveal:
0xa9176f8c076231fdb1a133eaebcc19eb316823c7ada999301e4e8fb68c799f4c770c015b15b8b7968fb342e7ae939d2e04092da2aad1ce6fd106411c3d447ffaa4085c080b5e446fa06cd6990380bad5aa4764690666cf7fa0c137aaa76400ab
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.103071885162428572 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.