← previous blocknext block →recent activity
Analyzing
Block #89,387,040
32 transactions · 25 stateful · 2026-07-22 08:33:20 UTC
Parallelism
75/100
Blocked
60%
Avg conflicts / tx
1.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #89,387,040 · 32 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
1w02w13w211w312w413w514w623w727w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18f9ee01…3ccb
0xd32edf…ff58
15 touches
28 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0xd5b10148…e637
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 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 0x18f9ee01a7…273ccb
Audit this contract →
← previous block·next block →recent activity