Block
#24283385
Status:
Finalized
Timestamp:
5 days ago (Jan-21-2026 01:12:35 PM +UTC)
Transactions:
311 transactions and 114 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
quasarbuilder in 12 secs
Block Reward:
0.007235703818691447 ETH (0 + 0.011794660808421459 - 0.004558956989730012)
Total Difficulty:
0
Size:
134,856 bytes
Gas Used:
27,603,557 (46.05%)
Gas Limit:
59,941,408
Base Fee Per Gas:
0.000000000165158316 ETH (0.165158316 Gwei)
Burnt Fees:
🔥 0.004558956989730012 ETH
Extra Data:
✨ Quasar (quasar.win) ✨ (Hex:0xe29ca82051756173617220287175617361722e77696e2920e29ca8)
Ether Price:
$2,979.98 / ETH
Hash:
0x13e391899b0fe5d323687bac4c8ce5e6f4fb8a0f120272884f946a1e017d116d
StateRoot:
0x2e763c2bbf25fc4c766d6331d19636ced678f9149c9f1a77f8c69a2e3b1303a7
WithdrawalsRoot:
0x5ad91dc37a8532f2283c4a294d194c8dec12e9ab6381db50fd7713c4d05af0d6
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x79a3d33a2c7d8d1700ee4cbc85094a2e6846650856053c24b7889e3d2d3610ea
Parent Root Hash:
0x363328f7fdfba6cf61ac3562e790fe2b44e498b39ea6ce83153f5a15b4ce5dab
Beacon Chain Deposit Count:
2045305
Slot Graffiti:
ssv.network GEabebTK1f73 (Hex:0x7373762e6e6574776f726b20474561626562544b316637330000000000000000)
Block Randomness:
0xc5fa27f1296cee75530b496733d5bc3c78592658052c6697db9556b9162fdd6e
Randao Reveal:
0x87c55cea0aec7a001dfbce3e41e8b68b4c43e88458ebc8416cb8d3f0d43c30a6cf964ac0a2d701cc766ee3ea1a3da916145b3c43d2009e24952438724ea30b08daf88623934815f7d98559022924a60e62cf210dc8420df05e207376f88aa62e
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.006386120233096211 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:
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.