← previous blocknext block →recent activity
Analyzing
Block #96,620,307
16 transactions · 15 stateful · 2026-08-16 23:25:00 UTC
Parallelism
63/100
Blocked
67%
Avg conflicts / tx
1.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,620,307 · 16 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
1w02w13w24w15w26w37w48w311w512w013w115w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x303c6660…6aa1
0x34b655…2a6f
8 touches
6 conflicts
0x02991b41…19e6
0x34b655…2a6f
8 touches
6 conflicts
0x56153262…21ce
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x0f6aef87…8137
0x34b655…2a6f
6 touches
3 conflicts
0x342fbbca…d443
0x40c49f…2af0
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity