← previous blocknext block →recent activity
Analyzing
Block #105,366,106
21 transactions · 20 stateful · 2026-09-16 16:24:06 UTC
Parallelism
81/100
Blocked
45%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,366,106 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w07w111w012w113w214w315w016w117w218w320w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05fe687b…b22c
0x6f6493…b480
8 touches
6 conflicts
0x07860b84…8cd7
0x6f6493…b480
8 touches
6 conflicts
0x0994d205…644b
0x6f6493…b480
8 touches
6 conflicts
0x0adb0a12…772f
0x6f6493…b480
8 touches
6 conflicts
0x0c1706dc…be58
0x6f6493…b480
8 touches
6 conflicts
0x1a4a5a36…7e4b
0x6f6493…b480
8 touches
6 conflicts
0x1e7b5cce…5394
0x6f6493…b480
8 touches
6 conflicts
0x24333479…f377
0x6f6493…b480
8 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: 0x6f6493e3…08b480
6 conflicts on slot 0x05fe687b2a…8eb22c
Audit this contract →
← previous block·next block →recent activity