← previous blocknext block →recent activity
Analyzing
Block #96,601,951
20 transactions · 14 stateful · 2026-08-16 21:52:41 UTC
Parallelism
65/100
Blocked
64%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,601,951 · 20 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
1w04w05w17w29w110w211w312w414w516w618w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5015cc64…d0ee
0xd32edf…ff58
11 touches
15 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0xa735b50a…fb2b
0x065c9d…c394
6 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x09beabbc…065e
0x188d58…ea8e
2 touches
0 conflicts
0x46cb45de…a566
0x188d58…ea8e
2 touches
0 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: FastLane: FastLaneAuctionHandler
15 conflicts on slot 0x5015cc64db…fbd0ee
Audit this contract →
← previous block·next block →recent activity