← previous blocknext block →recent activity
Analyzing
Block #106,421,692
25 transactions · 23 stateful · 2026-09-20 08:59:20 UTC
Parallelism
68/100
Blocked
43%
Avg conflicts / tx
1.32
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,421,692 · 25 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
3w04w05w17w18w29w315w419w220w321w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0df715f3…1601
0x34b655…2a6f
14 touches
21 conflicts
0xbe9d1d23…3de2
0x34b655…2a6f
10 touches
10 conflicts
0x4118bd12…924a
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x310a7246…2dcb
0x34b655…2a6f
8 touches
6 conflicts
0x524f0872…0d12
0x34b655…2a6f
8 touches
6 conflicts
0x1ab9db16…85dc
0x34b655…2a6f
8 touches
6 conflicts
0x7a903e28…f9ef
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 0x0df715f30f…1e1601
Audit this contract →
← previous block·next block →recent activity