Block
#17602608
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
986 days ago ()
Transactions:
134 transactions and 66 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
MEV Builder: 0x333...203 in 12 secs
Block Reward:
0.046603038857418832 ETH (0 + 0.23710104803483994 - 0.190498009177421108)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
62,848 bytes
Gas Used:
15,424,436 (51.41%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000012350403553 ETH (12.350403553 Gwei)
Burnt Fees:
🔥 0.190498009177421108 ETH
Extra Data:
rsync-builder.xyz (Hex:0x7273796e632d6275696c6465722e78797a)
Ether Price:
$1,924.30 / ETH
Hash:
0x98fc64a24da76037ec86bf3e4c8d7a15a3a374e3f8eec4dea27b40bb404220c0
StateRoot:
0xcccfcf6929372e5aa8fd081ef58e31a9cf150cecf931c1472f7252f98400c2c8
WithdrawalsRoot:
0x4161331284541127bd7e18cdde93fbbc8c08191b08393f87e44aa047679dc65c
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xd647fae21cfc4ca231e0d8fa5c97122d28e18ca81ca3aa5a35e17e4ed59b9e1e
Parent Root Hash:
0x40fd48e99345ff2de44485382e5af4a336085bbdeebc161f1fa6671a0d317ee2
Beacon Chain Deposit Count:
835438
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x3e3289f643765f2e86756c3c682391096b9a0d27b38cf2df2a8222095993ac70
Randao Reveal:
0x92df9d819f7ba47338a022a2be9708aba7e469620baadb16aa4aed8f034210f0ae0e05e5be7505c95c70390e2658446b002e6792cad91e20a900eea60f37bb6b5bbe5acf1a6c9095f76f9fe7f5798b0ea24c2a8752cab072b0e7479ab6395921
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.619071614292927045 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.