Block
#16479334
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
1380 days ago
Proposed On:
Block proposed on slot 5647619, epoch 176488
Transactions:
176 transactions and 67 contract internal transactions in this block
Fee Recipient:
MEV Builder: 0xBaF...e19 in 12 secs
Block Reward:
0.040287084854321085 ETH (0 + 0.336486917648225355 - 0.29619983279390427)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
81,551 bytes
Transaction Actions: Beta
Gas Used:
16,834,510 (56.12%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000017594799777 ETH (17.594799777 Gwei)
Burnt Fees:
🔥 0.29619983279390427 ETH
Extra Data:
Made on the moon by Blocknative (Hex:0x4d616465206f6e20746865206d6f6f6e20627920426c6f636b6e6174697665)
Ether Price:
$1,556.12 / ETH
Hash:
0xa526cc6fbc1ec6d9801da9771540ef2c802feb0d5cb813f10a4da2598e90efd9
StateRoot:
0x75c22fd2d6f99ae87b86fb0c1ac166fa82dd48e4bd2f17c52d2fce179ff8509b
Nonce:
0x0000000000000000
Slot:
5647619
Epoch:
176488
Proposer Index:
255434
Slot Root Hash:
0x065928f4f0334b2ee0bd9ed0ce2023f6995451b67b66494c7d411da06ccb0824
Parent Root Hash:
0xb8b25ac8e7c5b5366d6493cad61a5822fff9f436ab4685271448b7dda016bc6f
Beacon Chain Deposit Count:
519369
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x2b6bb1ee40d3679a0af7a30d2a0e5b6d371d3dd41a4ea1321b8302f5b2b9a33e
Randao Reveal:
0x958e255c3da087f1917edde11379bea019ddacc2593d95be696401103127e15010d7d4fd0e0bae4bb54b343d992f844e08a4b8014533c20cdfa78c21ebc5cf611d739e61355d0a865001c8f9ba2b6794ad650ebb2a6b896d4518108c596d1bcd
Proposer Fee Recipient:
0x2147d1156c28e7C6268e887C5fDC2360Ca078FbD (Fee Recipient: 0x21...FbD)
MEV Reward:
0.039794430460565085 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
Blob Utilisation:
Blob Gas Price:
Blob Gas Used:
Blob Gas Limit:
Total Blob Fees:
Excess Blob Gas:
Reserve Blob Base Fee:
| Rank | Participants | Txn Count | % Gas Used | Txn Fee (USD) |
|---|
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.