← previous blocknext block →recent activity
Analyzing
Block #106,570,208
23 transactions · 22 stateful · 2026-09-20 21:26:51 UTC
Parallelism
57/100
Blocked
55%
Avg conflicts / tx
1.87
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,570,208 · 23 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w18w29w313w414w517w618w719w820w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f561d8d…5e5f
0x34b655…2a6f
18 touches
36 conflicts
0x742436a7…c4d4
0x34b655…2a6f
12 touches
15 conflicts
0xfe2577ac…677b
0x34b655…2a6f
8 touches
6 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
8 touches
6 conflicts
0x7bf8320b…484c
0xd32edf…ff58
7 touches
6 conflicts
0x0f94ee4c…189d
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x17f18fe3…94e4
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 0x7f561d8ddd…745e5f
Audit this contract →
← previous block·next block →recent activity