← previous blocknext block →recent activity
Analyzing
Block #106,383,361
21 transactions · 20 stateful · 2026-09-20 05:46:27 UTC
Parallelism
76/100
Blocked
55%
Avg conflicts / tx
1.1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,383,361 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w311w013w314w415w016w117w218w319w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd9ba26b…108d
0x34b655…2a6f
10 touches
10 conflicts
0x02f5e3c0…d66d
0x6f6493…b480
8 touches
6 conflicts
0x06808d39…7e63
0x6f6493…b480
8 touches
6 conflicts
0x0bc46ffa…a205
0x6f6493…b480
8 touches
6 conflicts
0x0f802f7c…4b7f
0x6f6493…b480
8 touches
6 conflicts
0x138637ec…e77a
0x6f6493…b480
8 touches
6 conflicts
0x20e08a02…942b
0x6f6493…b480
8 touches
6 conflicts
0x24ff2e72…993a
0x6f6493…b480
8 touches
6 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
10 conflicts on slot 0xcd9ba26bf8…62108d
Audit this contract →
← previous block·next block →recent activity