← previous blocknext block →recent activity
Analyzing
Block #90,428,600
36 transactions · 26 stateful · 2026-07-26 07:40:50 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,428,600 · 36 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
2w03w14w25w36w310w212w414w415w520w630w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfdc0f83a…c736
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…002b
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001b
0x1b6862…e19c
10 touches
10 conflicts
0x9885a25f…2929
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 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 0xfdc0f83a4c…b1c736
Audit this contract →
← previous block·next block →recent activity