← previous blocknext block →recent activity
Analyzing
Block #106,253,104
23 transactions · 22 stateful · 2026-09-19 18:50:57 UTC
Parallelism
65/100
Blocked
55%
Avg conflicts / tx
1.74
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,253,104 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w07w19w110w212w313w214w315w416w517w618w721w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee56e2b2…7d47
0x34b655…2a6f
14 touches
21 conflicts
0xfccf4b5b…66ca
0x34b655…2a6f
14 touches
21 conflicts
0x80398c66…f3cc
0x34b655…2a6f
10 touches
10 conflicts
0x524f0872…0d12
0x34b655…2a6f
8 touches
6 conflicts
0x94e7f277…471b
0x34b655…2a6f
8 touches
6 conflicts
0x5906754f…b584
0x34b655…2a6f
8 touches
6 conflicts
0xc9cd7ba9…ee62
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 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: Perpl
21 conflicts on slot 0xee56e2b249…967d47
Audit this contract →
← previous block·next block →recent activity