← previous blocknext block →recent activity
Analyzing
Block #90,427,218
30 transactions · 25 stateful · 2026-07-26 07:33:43 UTC
Parallelism
83/100
Blocked
32%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,427,218 · 30 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w06w17w19w012w113w214w315w422w024w025w127w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ec819e9…336f
0xd32edf…ff58
9 touches
10 conflicts
0x6af306bb…2e81
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x10c19272…7442
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x6237f1a7…2f59
0x3bd359…433a
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
10 conflicts on slot 0x5ec819e9a9…6c336f
Audit this contract →
← previous block·next block →recent activity