Block
#20064890
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
625 days ago (Jun-11-2024 12:04:59 AM +UTC)
Transactions:
116 transactions and 43 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.023684001237732982 ETH (0 + 0.111717914576954719 - 0.088033913339221737)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
65,121 bytes
Gas Used:
8,617,473 (28.72%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000010215745769 ETH (10.215745769 Gwei)
Burnt Fees:
š„ 0.088033913339221737 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,497.32 / ETH
Hash:
0x65baff6f28e3382d1dab97be3ca09f2451a2efc766ac456000e93fd2c4a09a9e
StateRoot:
0xbd8811f512707a24d526876646e9788d533d28bf6b128991e2fe81708bfae2b3
WithdrawalsRoot:
0xdbef55f9b24293e3abb90a54cbfb697767b16bd34175a8b85a60b2eff3d7e2aa
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xad6ede98807702ceb160c8c17f7e63a977fafabd0ed29d596aae660a97471dfc
Parent Root Hash:
0xe976b1a87354b47262ed8e9ad9daa8d51a1cdfaef45eeb8e8af912d92e7d7411
Beacon Chain Deposit Count:
1527996
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x385a0626cff290dd8d8a5db45ba0605112e06a39a153822164c4bd5c2070bcc5
Randao Reveal:
0x968711c24d5268234d026dd9cc7b779b67d8fe7e9cb6fe5f642e9ae7e84d212111cf1d5ab576c3b47665144151f0c7ed02d1652cfa1320c782bc6699e3bdf5875b9190cc276c5900504b08e488014206109d324e8a170a8034cad4bd1d2051ee
Proposer Fee Recipient:
0xeBec795c9c8bBD61FFc14A6662944748F299cAcf (Fee Recipient: 0xeBe...Acf)
MEV Reward:
0.027741378115618725 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:
786,432 (6 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.