← previous blocknext block →recent activity
Analyzing
Block #91,958,931
28 transactions · 20 stateful · 2026-07-31 16:04:22 UTC
Parallelism
64/100
Blocked
70%
Avg conflicts / tx
1.64
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #91,958,931 · 28 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w48w111w513w615w718w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49c27bea…0177
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0x65bd5770…5ecc
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
36 conflicts on slot 0x49c27beab3…ad0177
Audit this contract →
← previous block·next block →recent activity