← previous blocknext block →recent activity
Analyzing
Block #105,857,920
21 transactions · 21 stateful · 2026-09-18 09:40:55 UTC
Parallelism
67/100
Blocked
48%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,857,920 · 21 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
1w03w04w16w110w211w312w413w514w615w016w117w219w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x8db32935…81a7
0x34b655…2a6f
10 touches
10 conflicts
0x282c7bf6…f709
0x34b655…2a6f
10 touches
10 conflicts
0xf06fce24…887d
0x34b655…2a6f
6 touches
3 conflicts
0x80398c66…f3cc
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xea79e6d3…68ad
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