Block
#20182004
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
617 days ago (Jun-27-2024 09:03:11 AM +UTC)
Transactions:
138 transactions and 50 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.0342027883366903 ETH (0 + 0.10421344079501362 - 0.07001065245832332)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
41,426 bytes
Gas Used:
13,872,129 (46.24%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.00000000504685708 ETH (5.04685708 Gwei)
Burnt Fees:
🔥 0.07001065245832332 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,445.80 / ETH
Hash:
0x9ec89f1c578742d2ee1ccde5ef601026a1dfd992f25d2686ac913e9c4430e610
StateRoot:
0x94124b52973f2f10ba6015686c352669ee604295e31ae1cde2436420924407d0
WithdrawalsRoot:
0x52bc9f80aa2fa8c2ab7727966696a886fea053b78be4459d02596ad89ec05d78
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x43021d1529f9fd0405ca6d428d6e3480cee82724acbd15f4345b03de3fa90511
Parent Root Hash:
0xe1f705461154c3a25d39b65c6cb719b9b4617e0e8a1c722f78d46895117c0f4e
Beacon Chain Deposit Count:
1559980
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x9de5c6854dc01271cd26dc58039f03a113fcafb906acebe467f246a507451795
Randao Reveal:
0x8b88b169aace034781cd984ff72fd52b9347c0c07d7e9ade4f0a1e138a2d80c23feac9e65c8638fc24ba383b7414c7fc190ab584629250ef335f0a2533032de55353a6c2a8d8ba046fb6c02ae980a8a16cd7ca0be1de085fe8bde87360d8141b
Proposer Fee Recipient:
0x25dFcFB061956c6f33B1ee032cc33837d0b83257 (Fee Recipient: 0x25df...257)
MEV Reward:
0.039797708948267728 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6 Blobs (100.00%)
Blob Gas Price:
494 wei (0.000000494 Gwei)
Blob Gas Used:
786,432 (100.00%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000388497408 ETH
Excess Blob Gas:
20,709,376 (158 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.