← previous blocknext block →recent activity
Analyzing
Block #97,612,804
17 transactions · 17 stateful · 2026-08-20 11:25:39 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,612,804 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w07w18w29w310w413w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05ec0ff9…eab5
0x34b655…2a6f
10 touches
10 conflicts
0x88724b87…5e65
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf15273a1…2c52
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x947bb79d…6458
0x34b655…2a6f
4 touches
1 conflict
0x953517cb…cdec
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
10 conflicts on slot 0x05ec0ff98f…64eab5
Audit this contract →
← previous block·next block →recent activity