← previous blocknext block →recent activity
Analyzing
Block #106,935,882
28 transactions · 25 stateful · 2026-09-22 04:08:20 UTC
Parallelism
75/100
Blocked
48%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,935,882 · 28 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
2w03w07w08w112w113w214w315w416w217w323w124w525w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9663b209…18e7
0x34b655…2a6f
12 touches
15 conflicts
0xd4230a60…bd13
0x34b655…2a6f
10 touches
10 conflicts
0xf7b76d2f…1b9c
0x34b655…2a6f
8 touches
6 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
8 touches
6 conflicts
0xa0f22c1c…bd53
0xd32edf…ff58
7 touches
6 conflicts
0x206f4379…e08a
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x4996be87…663a
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 0x9663b20932…c218e7
Audit this contract →
← previous block·next block →recent activity