← previous blocknext block →recent activity
Analyzing
Block #106,017,103
17 transactions · 17 stateful · 2026-09-18 23:03:08 UTC
Parallelism
65/100
Blocked
59%
Avg conflicts / tx
1.24
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,017,103 · 17 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
1w02w15w26w07w18w29w310w411w513w315w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a150a01…7f4c
0x6f6493…b480
11 touches
15 conflicts
0x12c9b41a…8eb9
0x6f6493…b480
11 touches
15 conflicts
0x1f71a92f…607c
0x6f6493…b480
11 touches
15 conflicts
0x20c3b7a7…73f6
0x6f6493…b480
11 touches
15 conflicts
0x2ceeb4bc…1330
0x6f6493…b480
11 touches
15 conflicts
0x2e85d1bf…21a1
0x6f6493…b480
11 touches
15 conflicts
0x2f9d4dc6…cc64
0x6f6493…b480
11 touches
15 conflicts
0x3234bae8…8012
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 0x0a150a012b…cc7f4c
Audit this contract →
← previous block·next block →recent activity