← previous blocknext block →recent activity
Analyzing
Block #106,549,305
20 transactions · 19 stateful · 2026-09-20 19:41:39 UTC
Parallelism
65/100
Blocked
58%
Avg conflicts / tx
1.45
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,549,305 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w17w19w210w111w012w313w414w515w618w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x07c47b1c…93c8
0x34b655…2a6f
10 touches
10 conflicts
0xd193364c…cd91
0x34b655…2a6f
8 touches
6 conflicts
0x91de4f4c…9277
0x34b655…2a6f
8 touches
6 conflicts
0x1cdfe548…d3aa
0x34b655…2a6f
8 touches
6 conflicts
0x67a56c8b…f955
0x34b655…2a6f
6 touches
3 conflicts
0x81878590…6d25
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity