← previous blocknext block →recent activity
Analyzing
Block #79,116,293
33 transactions · 24 stateful · 2026-06-04 17:41:07 UTC
Parallelism
82/100
Blocked
50%
Avg conflicts / tx
0.97
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #79,116,293 · 33 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w37w412w214w515w017w018w119w225w329w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x63e48b…53f2
12 touches
15 conflicts
0x00000000…0003
0x63e48b…53f2
12 touches
15 conflicts
0x9a555477…19a8
0x754704…b603
12 touches
15 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
12 touches
15 conflicts
0x00000000…0004
0x63e48b…53f2
12 touches
15 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xba1b5300…23bc
0xd32edf…ff58
7 touches
6 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: 0x63e48b72…8c53f2
15 conflicts on slot 0x0000000000…000000
Audit this contract →
← previous block·next block →recent activity