← previous blocknext block →recent activity
Analyzing
Block #106,923,726
25 transactions · 19 stateful · 2026-09-22 03:07:09 UTC
Parallelism
72/100
Blocked
47%
Avg conflicts / tx
0.76
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,923,726 · 25 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
1w03w15w211w012w113w214w315w416w517w621w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcc8f826…7c5f
0x34b655…2a6f
10 touches
10 conflicts
0xdd460daa…6b5b
0x34b655…2a6f
8 touches
6 conflicts
0xccebf5c5…8758
0x34b655…2a6f
8 touches
6 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x4996be87…663a
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
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
10 conflicts on slot 0xfcc8f826d7…5f7c5f
Audit this contract →
← previous block·next block →recent activity