← previous blocknext block →recent activity
Analyzing
Block #96,612,919
18 transactions · 16 stateful · 2026-08-16 22:47:51 UTC
Parallelism
61/100
Blocked
50%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,612,919 · 18 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
1w02w13w24w35w47w59w612w013w514w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x14cc64cc…b9f9
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0x8ea5a2b1…7a88
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcdc1731c…b91a
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
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: FastLane: FastLaneAuctionHandler
21 conflicts on slot 0x14cc64cc85…f6b9f9
Audit this contract →
← previous block·next block →recent activity