← previous blocknext block →recent activity
Analyzing
Block #93,186,170
41 transactions · 36 stateful · 2026-08-04 22:59:46 UTC
Parallelism
83/100
Blocked
53%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,186,170 · 41 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
1w02w13w210w311w413w414w515w616w017w122w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe612dced…f26f
0xd32edf…ff58
13 touches
21 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0x033cf007…136d
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0x2b093939…9085
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
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
21 conflicts on slot 0xe612dced11…60f26f
Audit this contract →
← previous block·next block →recent activity