← previous blocknext block →recent activity
Analyzing
Block #106,186,653
28 transactions · 25 stateful · 2026-09-19 13:16:25 UTC
Parallelism
68/100
Blocked
52%
Avg conflicts / tx
1.39
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,186,653 · 28 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
1w02w03w14w25w36w07w18w212w419w520w622w723w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c00c56d…fd1f
0x34b655…2a6f
12 touches
15 conflicts
0xd62f3741…b903
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
6 touches
3 conflicts
0x559b9b44…9024
0x34b655…2a6f
6 touches
3 conflicts
0x80a49a52…b8af
0x34b655…2a6f
6 touches
3 conflicts
0x8cc502a4…3f56
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
15 conflicts on slot 0x0c00c56daa…a9fd1f
Audit this contract →
← previous block·next block →recent activity