← previous blocknext block →recent activity
Analyzing
Block #106,958,148
26 transactions · 24 stateful · 2026-09-22 06:00:25 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
1.35
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,958,148 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w110w011w112w213w315w217w119w420w521w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4066ef6f…e3e2
0x34b655…2a6f
16 touches
28 conflicts
0x5e2ea201…12de
0x34b655…2a6f
16 touches
28 conflicts
0x01ad5dd0…11a1
0x34b655…2a6f
12 touches
15 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x1b3df55c…8693
0x34b655…2a6f
8 touches
6 conflicts
0x46483cb1…e7ca
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
28 conflicts on slot 0x4066ef6fd8…b1e3e2
Audit this contract →
← previous block·next block →recent activity