Sepolia Testnet

Block

#6320181
[ This is a Sepolia Testnet block only ]

Block Height:
6320181
Status:
Finalized
Timestamp:
Proposed On:
Block proposed on slot 5448781, epoch 170274
Transactions:
Withdrawals:
16 withdrawals in this block

Block Reward:
0.031260608582723301 ETH (0 + 0.276310507623913899 - 0.245049899041190598)
Total Difficulty:
17,000,018,015,853,232
Size:
172,671 bytes

Gas Used:
13,870,797 (46.24%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000017666605534 ETH (17.666605534 Gwei)
Burnt Fees:
🔥 0.245049899041190598 ETH
Extra Data:
reth/v1.0.0/linux (Hex:0x726574682f76312e302e302f6c696e7578)
Hash:
0xfaf4272563caaa23206296ac3891bbadffb15f056b083e4f5266b34408c38dfb
StateRoot:
0x146d7c6ab4591f00da7eca237c85c6934b634ec829c91391756f6a5f40475cf0
WithdrawalsRoot:
0xb934ec0feecfca8b05d81d74b4ba735f37f3978a7ae2b5df88751a8a014de221
Nonce:
0x0000000000000000

Slot:
5448781
Epoch:
170274
Proposer Index:
424

Slot Root Hash:
0x9a402288a9f6b81691b725a53e917f1cd9e48ff07f82c252bdd0fb95fecb3bdc
Parent Root Hash:
0x73c01c5a6da2cad54075ecc76886943fa1c539b229df1112d71a8fd4b94ad53a
Beacon Chain Deposit Count:
403
Slot Graffiti:
Lighthouse/v5.2.1-c6f8bf3 (Hex:0x4c69676874686f7573652f76352e322e312d6336663862663300000000000000)
Block Randomness:
0x2085cf7683d7bc58f33e53be2670916b7429d96f0f2d1afae4573765e93a8b06
Randao Reveal:
0xa9d3d27e19fe27dd01af76f5897e1d3c40e24797ccec58fecd908abf1d8ad295ef83bc18019213e3cbe62642d70a911203206e7f3e2c13fea1af02d97a6615bc3c763be3e83d8ddf3d001176db9fc4332af85e450e0c8a6efad348fabc2d4ae9
:
:
:
Blob Tx:
Blob Size:
640 KiB (5 blobs)
Blob Utilisation:
5 Blobs (83.33%)
Blob Gas Price:
0.000000000000003129 ETH (0.000003129 Gwei)
Blob Gas Used:
655,360 (83.33%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.00000000205062144 ETH
Excess Blob Gas:
26,869,760 (205 blobs)

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.