← previous blocknext block →recent activity
Analyzing
Block #96,608,162
25 transactions · 21 stateful · 2026-08-16 22:23:55 UTC
Parallelism
80/100
Blocked
57%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,608,162 · 25 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
1w02w16w27w28w39w010w111w214w216w017w118w219w321w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x033cf007…136d
0x34b655…2a6f
8 touches
6 conflicts
0x9c57d785…de69
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0xd8d828a7…b64f
0x1b6862…e19c
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 0x033cf007c8…d2136d
Audit this contract →
← previous block·next block →recent activity