← previous blocknext block →recent activity
Analyzing
Block #106,053,179
18 transactions · 16 stateful · 2026-09-19 02:04:41 UTC
Parallelism
61/100
Blocked
63%
Avg conflicts / tx
1.67
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,053,179 · 18 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
2w03w04w15w26w27w310w411w113w514w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd62f3741…b903
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x5ad3a514…8f64
0x34b655…2a6f
8 touches
6 conflicts
0xea79e6d3…68ad
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x4e58f1d6…2fca
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
10 conflicts on slot 0xd62f374157…55b903
Audit this contract →
← previous block·next block →recent activity