Block
#21860723
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
378 days ago (Feb-16-2025 06:23:35 PM +UTC)
Transactions:
199 transactions and 44 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.010397281974371562 ETH (0 + 0.023253332908017848 - 0.012856050933646286)
Total Difficulty:
0
Size:
57,566 bytes
Gas Used:
15,147,142 (42.28%)
Gas Limit:
35,824,397
Base Fee Per Gas:
0.000000000848744333 ETH (0.848744333 Gwei)
Burnt Fees:
🔥 0.012856050933646286 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$2,661.59 / ETH
Hash:
0x91a6f972242d384f8d7f887ef639fcbcaf17bfe710081f46ebe7ca4b63585bd7
StateRoot:
0xba4a7c80e7c0c49c2b3eabf70c9c487d4598057872a64d0fabf7ece428004f20
WithdrawalsRoot:
0x084218d27a6646905f924d3f8ff2efd0bd51c1939e6d2911e3ea86ab375e15ca
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xc0f15e40cf9b5e0da28525ac24b3eec5fb732102ca83ac31e465f17874043e9b
Parent Root Hash:
0x6a712059b6de9a7a89cf91fa492f45a80f3cb51f5655bc3c8b1a53a674c2222f
Beacon Chain Deposit Count:
1915090
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xb270129df45e6abe2fc9e8ab20fc71dd1aceac806ff7a7c696a0ca5a86b69411
Randao Reveal:
0x8964d3deb07c885d7ff9957eb3bd6612cf9210d8d4d0ab6be0dd557604418bbea5bcc4f8351c4b502607a2f1b9445ebd0edc5734a4f58f4e96f56f2b726d5b26a6d032d0ab209553522b1e4061168052a3f0d4b5200a514d7fc93e66939a13d4
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.012319162538761391 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
640 KiB (5 blobs)
Blob Utilisation:
5 Blobs (83.33%)
Blob Gas Price:
0.000000000894730908 ETH (0.894730908 Gwei)
Blob Gas Used:
655,360 (83.33%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.00058637084786688 ETH
Excess Blob Gas:
68,812,800 (525 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.