← previous blocknext block →recent activity
Analyzing
Block #96,603,638
30 transactions · 27 stateful · 2026-08-16 22:01:10 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
1.37
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #96,603,638 · 30 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
3w04w15w26w07w08w09w310w412w513w514w515w616w728w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaedae560…7f27
0x34b655…2a6f
14 touches
21 conflicts
0x02991b41…19e6
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x89999c15…fdac
0x34b655…2a6f
8 touches
6 conflicts
0x8a5ced1c…3b29
0x34b655…2a6f
6 touches
3 conflicts
0x9711e898…2b6d
0x34b655…2a6f
6 touches
3 conflicts
0xa4e9800f…4ab0
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
21 conflicts on slot 0xaedae560ed…aa7f27
Audit this contract →
← previous block·next block →recent activity