← previous blocknext block →recent activity
Analyzing
Block #106,415,161
20 transactions · 20 stateful · 2026-09-20 08:26:28 UTC
Parallelism
55/100
Blocked
55%
Avg conflicts / tx
1.35
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,415,161 · 20 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w17w29w310w011w112w314w415w516w617w718w219w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc9bc5e3…f916
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xfdd131fa…dbdb
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x46c14e01…ff09
0x34b655…2a6f
6 touches
3 conflicts
0xee4fe1f7…3ead
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
6 conflicts on slot 0xcc9bc5e35b…edf916
Audit this contract →
← previous block·next block →recent activity