← previous blocknext block →recent activity
Analyzing
Block #105,851,566
27 transactions · 26 stateful · 2026-09-18 09:08:57 UTC
Parallelism
63/100
Blocked
58%
Avg conflicts / tx
2.11
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,851,566 · 27 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w19w112w113w214w315w416w517w618w719w820w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81716ce9…095f
0x34b655…2a6f
20 touches
45 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x184151bf…b54f
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x0e7838ac…6a89
0x34b655…2a6f
8 touches
6 conflicts
0x206f4379…e08a
0x34b655…2a6f
8 touches
6 conflicts
0xcc5daa0a…b949
0x34b655…2a6f
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
45 conflicts on slot 0x81716ce924…61095f
Audit this contract →
← previous block·next block →recent activity