← previous blocknext block →recent activity
Analyzing
Block #106,356,871
23 transactions · 23 stateful · 2026-09-20 03:33:07 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,356,871 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w07w110w111w012w113w214w315w421w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36e15b1e…4e1d
0x6f6493…b480
9 touches
10 conflicts
0x3a9225b9…3607
0x6f6493…b480
9 touches
10 conflicts
0x3eea9be7…b4b7
0x6f6493…b480
9 touches
10 conflicts
0x41709c99…b63e
0x6f6493…b480
9 touches
10 conflicts
0x4840f3bf…85de
0x6f6493…b480
9 touches
10 conflicts
0x4db1c810…c6e2
0x6f6493…b480
9 touches
10 conflicts
0x4e0eb7c6…d840
0x6f6493…b480
9 touches
10 conflicts
0x55725491…465d
0x6f6493…b480
9 touches
10 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
10 conflicts on slot 0x36e15b1ee9…fc4e1d
Audit this contract →
← previous block·next block →recent activity