Sepolia Testnet

Block

#11365138
[ This is a Sepolia Testnet block only ]

Block Height:
11365138
Status:
Finalized
Timestamp:
Proposed On:
Block proposed on slot 10788782, epoch 337149
Transactions:
Withdrawals:
16 withdrawals in this block

Block Reward:
0.067681785738910782 ETH (0 + 0.067681785738910782 - 0)
Total Difficulty:
0
Size:
75,520 bytes

Gas Used:
36,903,403 (61.51%)
Gas Limit:
60,000,000
Base Fee Per Gas:
0.000000001051622755 ETH (1.051622755 Gwei)
Burnt Fees:
🔥 0 ETH
Extra Data:
ethrex 22.0.0 (Hex:0x6574687265782032322e302e30)
Hash:
0x135d967b4c9a998aa99d05731aa3f5cb05ef26cf130e1794ed49d9848377e8a6
StateRoot:
0x2a79fbfb592078428f9aa4b50942a48ec8163cba124dd01eee003fcf4fe871d0
WithdrawalsRoot:
0x3af37da5ac195db1a8f2078b8094c72454ed0f93bf9ad1fde6167ff3254e1932
Nonce:
0x0000000000000000

Slot:
10788782
Epoch:
337149
Proposer Index:
1988

Slot Root Hash:
0x370bf8d6525be45f101771fdbc21662b7fc7eca740a76fc0526b7e21970ed1a0
Parent Root Hash:
0x0f3dabe0213f1b1fb5c13fb7dd8d20ae8474b8369bf116368ac49026c4b5ffa8
Beacon Chain Deposit Count:
410
Slot Graffiti:
charon/v1.10.3-e60c838 (Hex:0x636861726f6e2f76312e31302e332d6536306338333800000000000000000000)
Block Randomness:
0xe4a724d84cf86be80ffe0c9d0c9850f1c22b927c0614bfe09afe4fe12cf50c16
Randao Reveal:
0xa9ca8059b319c3df4841cc625842d52f47917b147214855fcc800b0d7ae9a6d83b641f3f2500681e1be67d64802a95f60fe1f2a3dae786ac067207429a0915b39308c023e45873c789fdb348e2643543b7eb127ad13557ee4ff9e43102c880b1
:
:
:
Blob Tx:
Blob Size:
256 KiB (2 blobs)
Blob Utilisation:
2 Blobs (9.52%)
Blob Gas Price:
0.000000000063336003 ETH (0.063336003 Gwei)
Blob Gas Used:
262,144 (9.52%)
Blob Gas Limit:
2,752,512
Total Blob Fees:
0.000016603153170432 ETH
Excess Blob Gas:
209,903,015 (1,601 blobs)
Reserve Blob Base Fee:
0.000000000065726422 ETH (0.065726422 Gwei)

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.