Block
#19965531
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
673 days ago ()
Transactions:
115 transactions and 38 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.031768383088107851 ETH (0 + 0.128012404828841039 - 0.096244021740733188)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
40,708 bytes
Gas Used:
9,347,758 (31.16%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000010295947086 ETH (10.295947086 Gwei)
Burnt Fees:
🔥 0.096244021740733188 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,840.39 / ETH
Hash:
0x759c76f87c91481e7b5d989c418faa743c02181d1095765d308b94bc87cce608
StateRoot:
0x04c015c1363d9e3a7dd001f82161937f796489539b982aef90a362aec9b916ea
WithdrawalsRoot:
0x24c0c75360502a18cb091b18cae68e3ef8337edd41d7c0ca241695aaf675c7c7
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x4555ea3b92450129d2ee0d32326e92afb8a02388690f307355b09125a650f1d3
Parent Root Hash:
0x6be978e3f94a4ad3a237b2c92b5afbc8904382b9c5f13244adf3842bf182f1ea
Beacon Chain Deposit Count:
1489348
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x0f3e9760cd5fdbd48230166da04a26c371ddf59e65d307025fc732b0f38d778e
Randao Reveal:
0xa3846f5d4057494eb0deb24557ac3421e614ffb932bb2b4eb3189c0c38b3669bde63e304fd4ea246ba3095d4117e944f10c9e57244faffcf4aedd548ac1486a062ff07c6555a4e37e4b9687120b5e343c91a2edc6382069ca27113847fd4ce86
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.03072988082022705 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
512 KiB (4 blobs)
Blob Utilisation:
4 Blobs (66.67%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
524,288 (66.67%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000524288 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.