← previous blocknext block →recent activity
Analyzing
Block #97,602,651
23 transactions · 19 stateful · 2026-08-20 10:34:00 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,602,651 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w08w111w212w313w414w315w417w520w622w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80eee557…711d
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x505f57b4…6e2a
0x34b655…2a6f
8 touches
6 conflicts
0x35c84655…53e3
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x2e5cdd04…22ab
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
15 conflicts on slot 0x80eee55732…76711d
Audit this contract →
← previous block·next block →recent activity