← previous blocknext block →recent activity
Analyzing
Block #96,639,679
22 transactions · 21 stateful · 2026-08-17 01:02:26 UTC
Parallelism
64/100
Blocked
57%
Avg conflicts / tx
1.23
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,639,679 · 22 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
1w02w13w24w36w27w48w010w412w414w515w617w320w121w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3fbdbca7…4829
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x08636046…e60f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x93afca4c…b47f
0x1b6862…e19c
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: FastLane: FastLaneAuctionHandler
10 conflicts on slot 0x3fbdbca784…d54829
Audit this contract →
← previous block·next block →recent activity