← previous blocknext block →recent activity
Analyzing
Block #97,369,017
27 transactions · 21 stateful · 2026-08-19 14:32:59 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.59
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,369,017 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w211w012w315w416w524w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x379dc435…6616
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xfc64f24b…01d1
0x34b655…2a6f
8 touches
6 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
6 touches
3 conflicts
0x6771eae2…7014
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
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
6 conflicts on slot 0x379dc43545…336616
Audit this contract →
← previous block·next block →recent activity