Block
#20060291
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
656 days ago ()
Transactions:
137 transactions and 25 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
MEV Builder: 0x88c...34A in 12 secs
Block Reward:
0.032561880922335064 ETH (0 + 0.082785804236648736 - 0.050223923314313672)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
49,574 bytes
Gas Used:
11,482,513 (38.28%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000004373948744 ETH (4.373948744 Gwei)
Burnt Fees:
🔥 0.050223923314313672 ETH
Extra Data:
jetbldr.xyz (Hex:0x6a6574626c64722e78797a)
Ether Price:
$3,665.99 / ETH
Hash:
0x3d0be752b05190542bd2c4ad5de94489895cf65c9e072f33064b25d3ef0f1ec8
StateRoot:
0x80b2f0b9ca213017c0559e6ef01843cd2459d60c9ef69072b9f294b19d909627
WithdrawalsRoot:
0xacc89c0d2bd1f49aa95fff2652423288049b52e99e03cee8f9207f2cc1cec23c
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x48b196e9d75d2a15f99206e8d9d87372928cfda6ac4bb93e3b17e51231fdb0ab
Parent Root Hash:
0x7fb2f56a3c18b66a6cfbc2c7b774391251dd982dfd5b86d8e078eeb844bb24ff
Beacon Chain Deposit Count:
1527109
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xfad0bbf0c8b8461fc1a3521b657f30f1619f8c74b2945ce625969088bf86b1ba
Randao Reveal:
0x89442b98b8cdf62bacdadb212d224d36469b52901e44ca163fdf4d1a023d040f9fe618bc6b0d91eda8c713ed44b4a0a310b363934c9b738c292283ea439cc26cc1fac9c5791cacaea6a6a3b25bf3ba4b3ef910059cf4e7320a319af194c302c9
Proposer Fee Recipient:
0x4675C7e5BaAFBFFbca748158bEcBA61ef3b0a263 (Coinbase: MEV Builder)
MEV Reward:
0.036263069643074413 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6 Blobs (100.00%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
786,432 (100.00%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000786432 ETH
Excess Blob Gas:
1,310,720 (10 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.