Block
#19995470
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
634 days ago (Jun-01-2024 07:27:11 AM +UTC)
Transactions:
167 transactions and 72 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.025351576465103764 ETH (0 + 0.159840590197353189 - 0.134489013732249425)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
119,135 bytes
Gas Used:
29,995,325 (99.98%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000004483665829 ETH (4.483665829 Gwei)
Burnt Fees:
š„ 0.134489013732249425 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,812.81 / ETH
Hash:
0xbd806e57e908b30788198aefd035b51521cf6c645e8cd9995c6a11d58cc02934
StateRoot:
0x3313e1f215125c927faa29bf6bc4363d7c58aed7ca723ae09f5cbfe21decf35d
WithdrawalsRoot:
0x5e961f3dc87b1dad1f94f0e769192c9bd58df4c9dfd4fd050856ae90cc9a4151
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xb786372552d98805608aabcf26be86dbd5fe94445868b05bf1898a517f651e06
Parent Root Hash:
0x5011c3c9b542cc424078f27bc08c4854173f54fdc4f0384e16f58f4288a16d87
Beacon Chain Deposit Count:
1504916
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xbf54ce1f18eed9c69e36f795a9e54f3c0f4e5d239cbaf16627616c27455aef7c
Randao Reveal:
0x86695f1c2ff3653f9c83a684b565d1e4739c61b51b6c16cbb333fb68634b5618831235ef7ed91126c9819816df68e1961701f52b0ae775de75b88056d0cb9ccca96f315e6a50bd24913667ae741df6bf0492225b911fbcbb2b64ffb2418508ea
Proposer Fee Recipient:
0x2194331af2cF9dE9Adb36cf09654faD65cafb58b (MEV Builder: 0x219...58b)
MEV Reward:
0.034164866445056654 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
384 KiB (3 blobs)
Blob Utilisation:
3 Blobs (50.00%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
393,216 (50.00%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000393216 ETH
Excess Blob Gas:
1,966,080 (15 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.