← previous blocknext block →recent activity
Analyzing
Block #105,840,966
22 transactions · 20 stateful · 2026-09-18 08:15:27 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.14
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,840,966 · 22 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
1w02w13w24w05w19w010w111w012w113w214w315w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x408db73d…6e90
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xb482658a…e4f5
0x34b655…2a6f
10 touches
10 conflicts
0x9513aafb…bb7f
0x34b655…2a6f
10 touches
10 conflicts
0x4118bd12…924a
0x34b655…2a6f
10 touches
10 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
10 touches
10 conflicts
0x60a536a6…ef7a
0x34b655…2a6f
8 touches
6 conflicts
0xffee49e7…f31f
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
15 conflicts on slot 0x408db73d0b…136e90
Audit this contract →
← previous block·next block →recent activity