Block
#22139073
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
325 days ago (Mar-27-2025 03:13:35 PM +UTC)
Transactions:
128 transactions and 25 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.014400801724731052 ETH (0 + 0.03547425760112454 - 0.021073455876393488)
Total Difficulty:
0
Size:
145,320 bytes
Gas Used:
13,238,228 (36.88%)
Gas Limit:
35,894,294
Base Fee Per Gas:
0.000000001591863796 ETH (1.591863796 Gwei)
Burnt Fees:
🔥 0.021073455876393488 ETH
Extra Data:
rsync-builder.xyz (Hex:0x7273796e632d6275696c6465722e78797a)
Ether Price:
$2,003.30 / ETH
Hash:
0x5dd1e077cb92c42527504d8b704550e50d514c4eaf63b3eae03e6acc006b9b78
StateRoot:
0x9ab3dbb3d8c8113b841faa0bc86fc54a426c1c0944dbcfb42cb2466b4bfe6a01
WithdrawalsRoot:
0x9dc48018fdb2e5450e87294a470ce1ab7fc3a9fa6aae879f932d4b4ef47c7a21
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x33c6a28f8683c51feeeeb2e7489c9a2afe46976b94513bb606614403cf19c227
Parent Root Hash:
0x25a4f31a850358592d71e7a25f97c0c0f9a7fa3952f7c7d341881d99cfa3680c
Beacon Chain Deposit Count:
1988382
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x4a05a289f1debdb1a0fae89e6a1552f0e8284ccf9c8c670f105b54cbf04e4217
Randao Reveal:
0x9649b982ff389b02a385dc8e7b4ef49600ac3669edc7bcce65a807144ab7747e899061372a49725c8d4869b051f33f5619ceaeb4b45d4194c461ca4893fddae072edab132c34da871c1a42c509502404cdf0dc83daa45b0a1e1a6ddf625b2e88
Proposer Fee Recipient:
0x4675C7e5BaAFBFFbca748158bEcBA61ef3b0a263 (Coinbase: MEV Builder)
MEV Reward:
0.054669223309673032 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
128 KiB (1 blobs)
Blob Utilisation:
1 Blobs (16.67%)
Blob Gas Price:
0.000000000000045173 ETH (0.000045173 Gwei)
Blob Gas Used:
131,072 (16.67%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000005920915456 ETH
Excess Blob Gas:
35,782,656 (273 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.