Block
#18248362
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
887 days ago (Sep-30-2023 11:56:11 AM +UTC)
Transactions:
163 transactions and 86 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.056454976147523611 ETH (0 + 0.147596365701609916 - 0.091141389554086305)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
127,484 bytes
Gas Used:
14,675,829 (48.92%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000006210306045 ETH (6.210306045 Gwei)
Burnt Fees:
🔥 0.091141389554086305 ETH
Extra Data:
@builder0x69 (Hex:0x406275696c64657230783639)
Ether Price:
$1,670.97 / ETH
Hash:
0xf507213f3957b817c87182c169d8e0e631109560dc9a972649bc2877daaa9f96
StateRoot:
0xa4bad4e81a801c6a05a53f51056d2c2662278428027d629c2314316f806c2a99
WithdrawalsRoot:
0x6f187bb7b2a4fdc8e81260b424f0e94b975a455200b54fef2ff5c66f0607930a
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x95f4ad8aac94fdc1a60399abb45399a667e6be27110c10cb6d2c02af984b8b89
Parent Root Hash:
0xa1c14c3af1ccad499c41cb1b4c8466408d62661119ca7fa64d2d30d32a909076
Beacon Chain Deposit Count:
981951
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xe7b58fe14987479acc5926b00e6bc93b324cc9b33ef55533abb3f73c4425605a
Randao Reveal:
0xb3d06070e5dc4945f8c4eef93b15983332fd70a9dc6e63e4f85f2cbf4cd3252375ec95fe8fea0ebdc0c5df62019666b101b8b12e02908e4af605c157f32ff951564f0f1ffd01cf93f47b93cf3a94d7c008a80beeae47646b4028f3946f15e237
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.058901917733269362 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.