← previous blocknext block →recent activity
Analyzing
Block #97,397,170
33 transactions · 27 stateful · 2026-08-19 17:15:49 UTC
Parallelism
88/100
Blocked
41%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,397,170 · 33 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w09w110w011w012w113w214w315w216w121w224w225w329w030w132w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f6aa736…a698
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00f7e3b7…e017
0x188d58…ea8e
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x097f22fa…0e46
0x34b655…2a6f
4 touches
1 conflict
0x52dad770…4ac9
0x34b655…2a6f
4 touches
1 conflict
0xbdcff57a…6ea3
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
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 0x6f6aa736ef…34a698
Audit this contract →
← previous block·next block →recent activity