← previous blocknext block →recent activity
Analyzing
Block #109,177,638
22 transactions · 17 stateful · 2026-09-30 00:21:27 UTC
Parallelism
64/100
Blocked
47%
Avg conflicts / tx
1.27
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #109,177,638 · 22 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
2w04w16w28w310w412w518w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d9ef283…ddd1
0x34b655…2a6f
14 touches
21 conflicts
0xf6cc3bca…ef71
0x34b655…2a6f
14 touches
21 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
10 touches
10 conflicts
0x5969523e…5191
0x34b655…2a6f
10 touches
10 conflicts
0xce307d4a…b8d8
0x34b655…2a6f
10 touches
10 conflicts
0xe27a259d…31a8
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0x7d9ef2836a…01ddd1
Audit this contract →
← previous block·next block →recent activity