Block
#20134667
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
645 days ago ()
Transactions:
173 transactions and 60 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.056276773499657737 ETH (0 + 0.216854092465317287 - 0.16057731896565955)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
63,293 bytes
Gas Used:
19,085,725 (63.62%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000008413477558 ETH (8.413477558 Gwei)
Burnt Fees:
🔥 0.16057731896565955 ETH
Extra Data:
rsync-builder.xyz (Hex:0x7273796e632d6275696c6465722e78797a)
Ether Price:
$3,510.94 / ETH
Hash:
0x07e064c94dd8712ff4d30b2bfff7b95608c1935adaf1f09ddaded6962eac24cd
StateRoot:
0x13571f1e67c370f2e3fcb2e8366c228b80258845e48da3d92c294d21c896a1b0
WithdrawalsRoot:
0xecdd1acbdcb02a093b516ea3ba9bec0ed60a135a003145facc39eb99cc0f600d
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xe1e9d51a92fb148ccf65e9673017833471722d48994a49f0378f9f34edcfcb16
Parent Root Hash:
0x1b44b4ee083873559fa5b00ea58fd38779ba9585eb8bdf6fac1da7a9901409f8
Beacon Chain Deposit Count:
1547493
Slot Graffiti:
Twinstake (Hex:0x5477696e7374616b650000000000000000000000000000000000000000000000)
Block Randomness:
0x9e94be2f9c2c16559f0d51f16363d5b0f6f30427bdc723b1ac2d52b54241a0ce
Randao Reveal:
0x86a1a63fd8c3db9b60bfe9d8f5c854e5b99e0a1314ef844f34312facad616da815d225e729997f6097f1677f7f8b6094161093384ba8f9b2c85e1e18358fea98347044fbe07a37d7fdf4f3b4a198704aaa511cd2fab37ccff7df160b6ccc5fa9
Proposer Fee Recipient:
MEV Reward:
0.055899471202536616 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
128 KiB (1 blobs)
Blob Utilisation:
1 Blobs (16.67%)
Blob Gas Price:
0.000000041944500754 ETH (41.944500754 Gwei)
Blob Gas Used:
131,072 (16.67%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.00549774960282829 ETH
Excess Blob Gas:
81,657,856 (623 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.