← previous blocknext block →recent activity
Analyzing
Block #106,936,134
20 transactions · 19 stateful · 2026-09-22 04:09:36 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
1.7
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,936,134 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w17w28w39w410w112w216w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74a03cbb…f5fe
0x34b655…2a6f
14 touches
21 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
12 touches
15 conflicts
0x34c48330…703f
0x34b655…2a6f
10 touches
10 conflicts
0xa9988419…9f45
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xcb21158b…f18d
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x4d71729b…b045
0x34b655…2a6f
4 touches
1 conflict
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 0x74a03cbb22…36f5fe
Audit this contract →
← previous block·next block →recent activity