← previous blocknext block →recent activity
Analyzing
Block #96,825,326
21 transactions · 18 stateful · 2026-08-17 16:36:10 UTC
Parallelism
71/100
Blocked
56%
Avg conflicts / tx
1.38
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,825,326 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w59w311w412w520w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
12 touches
15 conflicts
0x216ffe66…1f94
0x34b655…2a6f
10 touches
10 conflicts
0x628359b1…7263
0x34b655…2a6f
10 touches
10 conflicts
0x74d6c8dd…1695
0x34b655…2a6f
10 touches
10 conflicts
0x13cf2ac6…5a01
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0x1a2055c7…9054
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity