← previous blocknext block →recent activity
Analyzing
Block #97,740,858
35 transactions · 32 stateful · 2026-08-20 22:19:44 UTC
Parallelism
80/100
Blocked
63%
Avg conflicts / tx
1.06
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,740,858 · 35 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
2w05w06w07w18w29w310w011w112w113w214w316w017w018w119w120w222w125w428w229w434w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40ac662f…df77
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x0e1d0aa7…c6a4
0xd32edf…ff58
7 touches
6 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
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 0x40ac662f45…43df77
Audit this contract →
← previous block·next block →recent activity