← previous blocknext block →recent activity
Analyzing
Block #90,067,264
24 transactions · 22 stateful · 2026-07-25 01:05:42 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.46
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,067,264 · 24 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
1w02w13w24w35w410w111w512w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c1880e0…ed4e
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x34ab11f0…f529
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21c3
0x1b6862…e19c
6 touches
3 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
28 conflicts on slot 0x7c1880e004…3ded4e
Audit this contract →
← previous block·next block →recent activity