← previous blocknext block →recent activity
Analyzing
Block #89,865,494
23 transactions · 22 stateful · 2026-07-24 08:09:18 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
0.91
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,865,494 · 23 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
1w02w13w24w36w410w012w113w214w417w318w019w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b1fb73d…381c
0xd32edf…ff58
9 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x4ca2a6c3…ab80
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
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 0x6b1fb73d1d…8d381c
Audit this contract →
← previous block·next block →recent activity