← previous blocknext block →recent activity
Analyzing
Block #90,789,521
21 transactions · 19 stateful · 2026-07-27 13:58:04 UTC
Parallelism
71/100
Blocked
37%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,789,521 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w310w311w413w014w015w118w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x408f12fa…9ad2
0xd32edf…ff58
7 touches
6 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x0871ccae…fc76
0xa6afd3…d132
5 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x5a3732cb…edae
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
6 conflicts on slot 0x408f12fa7e…299ad2
Audit this contract →
← previous block·next block →recent activity