← previous blocknext block →recent activity
Analyzing
Block #105,845,662
24 transactions · 23 stateful · 2026-09-18 08:39:14 UTC
Parallelism
58/100
Blocked
39%
Avg conflicts / tx
1.71
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,845,662 · 24 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
1w08w113w214w315w416w517w618w719w820w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a548af5…0eb0
0x34b655…2a6f
16 touches
28 conflicts
0xd02dae7c…87ef
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x80398c66…f3cc
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x39479d9f…8985
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xeebacabb…a34c
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
28 conflicts on slot 0x5a548af508…f00eb0
Audit this contract →
← previous block·next block →recent activity