← previous blocknext block →recent activity
Analyzing
Block #90,286,213
20 transactions · 20 stateful · 2026-07-25 19:32:14 UTC
Parallelism
80/100
Blocked
30%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,286,213 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w311w013w015w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x28e2657d…c333
0xd32edf…ff58
7 touches
6 conflicts
0x4347ef7b…78f9
0x40c49f…2af0
5 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x1da7723c…80a7
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x3a921be0…779c
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 0x28e2657d1d…90c333
Audit this contract →
← previous block·next block →recent activity