← previous blocknext block →recent activity
Analyzing
Block #96,639,626
27 transactions · 24 stateful · 2026-08-17 01:02:10 UTC
Parallelism
70/100
Blocked
63%
Avg conflicts / tx
1.56
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,639,626 · 27 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w59w113w618w521w622w625w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x32e25111…16a2
0xd32edf…ff58
13 touches
21 conflicts
0xea1b8c07…b969
0x34b655…2a6f
8 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: FastLane: FastLaneAuctionHandler
21 conflicts on slot 0x32e251110f…d216a2
Audit this contract →
← previous block·next block →recent activity