← previous blocknext block →recent activity
Analyzing
Block #97,562,080
18 transactions · 17 stateful · 2026-08-20 07:08:38 UTC
Parallelism
61/100
Blocked
59%
Avg conflicts / tx
1.22
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,562,080 · 18 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
1w03w04w15w26w07w38w19w410w511w512w616w317w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d120d…7084
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x288a48ad…8275
0x34b655…2a6f
4 touches
1 conflict
0x60a536a6…ef7a
0x34b655…2a6f
4 touches
1 conflict
0x639bbfca…4218
0x34b655…2a6f
4 touches
1 conflict
0x6737ee07…9978
0x34b655…2a6f
4 touches
1 conflict
0x728f999a…832f
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 0xec7d120df9…5d7084
Audit this contract →
← previous block·next block →recent activity