Block
#20197377
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
624 days ago ()
Transactions:
142 transactions and 38 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
MEV Builder: 0x88c...34A in 12 secs
Block Reward:
0.022181438888636447 ETH (0 + 0.044211255900562277 - 0.02202981701192583)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
51,997 bytes
Gas Used:
11,063,915 (36.88%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000001991141202 ETH (1.991141202 Gwei)
Burnt Fees:
🔥 0.02202981701192583 ETH
Extra Data:
jetbldr.xyz (Hex:0x6a6574626c64722e78797a)
Ether Price:
$3,373.52 / ETH
Hash:
0x0a37065f46956284e0382071fb236952004d286dad3b03e088a67fd7102b5859
StateRoot:
0x8b6d1ccae1a0ae38869b204eae8d0be5b282b5e6b1797fe1a66ceee38c171daf
WithdrawalsRoot:
0x10c5ad6cd00b3e216a5abb5add93e886b5f83ac49caa7796241a192154b87d77
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x5c5e3d59c29cc0713ae3f635b1e1c81bd2ebc165a7aa73c75149e4aa220b0635
Parent Root Hash:
0xb34f672fffb3c622c182a404668743f1ffdd49dad67cf7d9cdb8591a376af6a3
Beacon Chain Deposit Count:
1564736
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x39d7680efb8900ed3bae1c294a2e3deb736fc57fe8a90ec132a6b7c7391f531c
Randao Reveal:
0x9645c2a6848c9589f2af894ae3306d1876565f1a9bdbc6a79459b759a5f9c37a4bf67b3df7638be79b3db02d1fe58bd001891b23f2556c37312b816a27cea22ee2acef357db980b2266a410b352ab7f02c0533af63d8394a21fb27cf5e808d04
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.022100555395892046 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.