← previous blocknext block →recent activity
Analyzing
Block #106,575,714
21 transactions · 20 stateful · 2026-09-20 21:54:33 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,575,714 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w16w27w210w214w015w116w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe399ba21…29ab
0x34b655…2a6f
10 touches
10 conflicts
0xe5eb3c33…0e3a
0x34b655…2a6f
8 touches
6 conflicts
0x3b6e959d…158f
0x34b655…2a6f
8 touches
6 conflicts
0x5fe04cc2…7148
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x8f63f383…6eda
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x159cff26…7665
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
10 conflicts on slot 0xe399ba2163…8b29ab
Audit this contract →
← previous block·next block →recent activity