← previous blocknext block →recent activity
Analyzing
Block #106,008,708
13 transactions · 13 stateful · 2026-09-18 22:20:54 UTC
Parallelism
54/100
Blocked
62%
Avg conflicts / tx
1.38
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,008,708 · 13 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
1w02w13w25w06w07w18w29w310w411w512w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a3f8e8e…6ce5
0x6f6493…b480
11 touches
15 conflicts
0x0b153918…b64a
0x6f6493…b480
11 touches
15 conflicts
0x0e93ebd2…9df4
0x6f6493…b480
11 touches
15 conflicts
0x0fe897dd…90cb
0x6f6493…b480
11 touches
15 conflicts
0x157bf13c…b475
0x6f6493…b480
11 touches
15 conflicts
0x157bf13c…b479
0x6f6493…b480
11 touches
15 conflicts
0x19e3db03…aab4
0x6f6493…b480
11 touches
15 conflicts
0x2caee10c…dd46
0x6f6493…b480
11 touches
15 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: 0x6f6493e3…08b480
15 conflicts on slot 0x0a3f8e8ea2…a96ce5
Audit this contract →
← previous block·next block →recent activity