← previous blocknext block →recent activity
Analyzing
Block #91,027,183
20 transactions · 16 stateful · 2026-07-28 09:54:37 UTC
Parallelism
60/100
Blocked
56%
Avg conflicts / tx
1.35
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,027,183 · 20 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
2w03w14w25w36w47w58w69w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd0221fe4…46fa
0xd32edf…ff58
13 touches
21 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x86cdf24e…3394
0x065c9d…c394
5 touches
3 conflicts
0x00f7e3b7…e015
0x188d58…ea8e
4 touches
1 conflict
0x00f7e3b7…e017
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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 0xd0221fe4e1…aa46fa
Audit this contract →
← previous block·next block →recent activity