← previous blocknext block →recent activity
Analyzing
Block #94,972,139
20 transactions · 17 stateful · 2026-08-11 04:58:50 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1.35
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,972,139 · 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
1w02w13w24w38w49w511w614w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x172b84ba…50f7
0xd32edf…ff58
13 touches
21 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x7cf7efa2…05f7
0x851145…3f07
6 touches
3 conflicts
0x11b69a7e…334e
0x01bff4…1071
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0x90daac72…db7a
0x754704…b603
4 touches
1 conflict
0x3d9eb674…b3fb
0x754704…b603
4 touches
1 conflict
0x0edf889a…ce9d
0x01bff4…1071
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 0x172b84ba88…8550f7
Audit this contract →
← previous block·next block →recent activity