← previous blocknext block →recent activity
Analyzing
Block #96,031,329
21 transactions · 21 stateful · 2026-08-14 22:02:19 UTC
Parallelism
81/100
Blocked
57%
Avg conflicts / tx
1.05
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,031,329 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w16w07w18w29w110w011w112w215w319w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7da6eb60…b34e
0x34b655…2a6f
8 touches
6 conflicts
0x4962952b…b8be
0xd32edf…ff58
7 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xf5ea108a…dbf6
0x34b655…2a6f
6 touches
3 conflicts
0xb566e26f…6d5d
0x34b655…2a6f
6 touches
3 conflicts
0x58e06bab…34ce
0x1b6862…e19c
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
6 conflicts on slot 0x7da6eb601b…b3b34e
Audit this contract →
← previous block·next block →recent activity