← previous blocknext block →recent activity
Analyzing
Block #106,570,370
27 transactions · 26 stateful · 2026-09-20 21:27:40 UTC
Parallelism
78/100
Blocked
46%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,570,370 · 27 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
1w02w13w04w15w16w27w09w111w216w018w119w220w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50de0015…275c
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x6352bcf7…67ec
0x34b655…2a6f
8 touches
6 conflicts
0x2c2761c0…476e
0x34b655…2a6f
8 touches
6 conflicts
0x7d6b9af1…9a38
0x34b655…2a6f
8 touches
6 conflicts
0xfe2577ac…677b
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xe2052b9a…d7cb
0x34b655…2a6f
8 touches
6 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 0x50de001558…88275c
Audit this contract →
← previous block·next block →recent activity