Block
#20198032
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
578 days ago (Jun-29-2024 02:47:47 PM +UTC)
Transactions:
127 transactions and 42 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.012844832350028378 ETH (0 + 0.057648429562448818 - 0.04480359721242044)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
54,327 bytes
Gas Used:
12,140,860 (40.47%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000003690314954 ETH (3.690314954 Gwei)
Burnt Fees:
š„ 0.04480359721242044 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,373.52 / ETH
Hash:
0x12f3470caf0680b32f2b34cd4abb528a5cd9a49f23f46f480154b9631c473c93
StateRoot:
0x7d194d68cd43e425a200bee01223d7c7df3748cbb25736ee85393a53cd9f7e81
WithdrawalsRoot:
0x7368209ef0777dca44e8ec3616793fdd47c23cd123fabdf67494649d77016120
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x1b25e7efcbcaff84b41d94f8a7681652137ae88ea5481c4a85e18454e756cc60
Parent Root Hash:
0xc2fd230f736f8c6231224036787ebfe8f9ce25371e8088f183b98e221881ea64
Beacon Chain Deposit Count:
1564736
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x2044c08188c4d10ae800e4fed5f8a52a7891ad0a641711104c97e92bf417d040
Randao Reveal:
0xa81e88414b967beefced60c86314749cb3e4d2d1f529431bff2bf05d0878a87137c116b3c95c275d65cf47d05a85b5a707937c3e1def907fcc555ed100b4e1b54248699ca97cde926e74fd0090c7ccdc9bfcc2c4ba6bbb06aef97f6c3274b936
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.016208519954363226 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
512 KiB (4 blobs)
Blob Utilisation:
4 Blobs (66.67%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
524,288 (66.67%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000524288 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.