← previous blocknext block →recent activity
Analyzing
Block #106,917,603
30 transactions · 29 stateful · 2026-09-22 02:36:20 UTC
Parallelism
73/100
Blocked
55%
Avg conflicts / tx
1.7
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,917,603 · 30 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
2w03w15w06w17w08w19w210w311w412w513w614w221w724w325w426w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69411fb3…e36d
0x34b655…2a6f
16 touches
28 conflicts
0x91685a55…a18b
0x34b655…2a6f
12 touches
15 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
12 touches
15 conflicts
0x70986451…c6bd
0x34b655…2a6f
10 touches
10 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
10 touches
10 conflicts
0x62f53694…128d
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xadfac54b…b370
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
28 conflicts on slot 0x69411fb3ba…bce36d
Audit this contract →
← previous block·next block →recent activity