← previous blocknext block →recent activity
Analyzing
Block #106,370,021
24 transactions · 23 stateful · 2026-09-20 04:39:18 UTC
Parallelism
63/100
Blocked
48%
Avg conflicts / tx
1.79
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,370,021 · 24 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w27w312w416w417w518w619w720w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76aac745…357d
0x34b655…2a6f
18 touches
36 conflicts
0x89eaf36a…4e48
0x34b655…2a6f
14 touches
21 conflicts
0x2c2761c0…476e
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
6 touches
3 conflicts
0xcd9ba26b…108d
0x34b655…2a6f
6 touches
3 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
6 touches
3 conflicts
0x377b5b72…73d4
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 0x76aac74552…f2357d
Audit this contract →
← previous block·next block →recent activity