Block
#19661602
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
679 days ago (Apr-15-2024 02:48:11 PM +UTC)
Transactions:
170 transactions and 90 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.038297966612568494 ETH (0 + 0.496471227160928249 - 0.458173260548359755)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
161,940 bytes
Gas Used:
17,128,965 (57.10%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000026748449807 ETH (26.748449807 Gwei)
Burnt Fees:
š„ 0.458173260548359755 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,103.00 / ETH
Hash:
0x47fa384ab6c7277427c13d407b9f57774c79080bd9d75b140400eb70680ccf0d
StateRoot:
0x2117e87c0325177b9da72677aced3cfbb8eea8a80f18e32f6f54df9f7c71f8ca
WithdrawalsRoot:
0x98c0fbfff4366cddff72c5e7d1f099af139753b2491d6fc0ce942840e1370cc7
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xbe197210a041f01a89efcc64edbed90b658fd724497b1b6c06e8bf53ca16eb3f
Parent Root Hash:
0x5501e506b7bb0f3ab6ddb50092e3d3b6362376f2f2c8ada1e8124a6b254613ec
Beacon Chain Deposit Count:
1437570
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x1c0ac45827e3ba758081e41ecfbee9c5c23a58cd46cba3ac0ef3a10d68f1a477
Randao Reveal:
0x8d53f0b8766eb4db5b5a9bd939dc06f88cd5f2e1e429d686f577acdef620f73679c3a307cb48ffc3419e99d17ae7b64e19e3720776ec4a6b3e9bf2c04853f00ee65b95273d5319da921fce87ad8937d709281072270da1aa9549e8837a720250
Proposer Fee Recipient:
0x51a1449b3B6D635EddeC781cD47a99221712De97 (Fee Recipient: 0x51...e97)
MEV Reward:
0.23911207718658976 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:
393,216 (3 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.