← previous blocknext block →recent activity
Analyzing
Block #106,216,905
29 transactions · 27 stateful · 2026-09-19 15:48:43 UTC
Parallelism
62/100
Blocked
56%
Avg conflicts / tx
2.21
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,216,905 · 29 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w27w311w116w517w618w719w821w922w1027w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf99856c4…370d
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc8d6ce37…b16b
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x4abfb389…18f4
0x34b655…2a6f
6 touches
3 conflicts
0x1a84e266…4f8a
0x34b655…2a6f
6 touches
3 conflicts
0x70e89205…5121
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
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
36 conflicts on slot 0xf99856c491…9a370d
Audit this contract →
← previous block·next block →recent activity