← previous blocknext block →recent activity
Analyzing
Block #87,622,197
15 transactions · 14 stateful · 2026-07-14 03:48:54 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,622,197 · 15 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
1w02w13w24w38w09w112w213w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x835f7c91…0d28
0xd32edf…ff58
7 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xfde133d7…5e63
0x34b655…2a6f
6 touches
3 conflicts
0x28ca7f51…a5fa
0x065c9d…c394
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x07ed27ca…3903
0x34b655…2a6f
4 touches
1 conflict
0x410b84ab…1dbc
0x34b655…2a6f
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 0x835f7c911f…870d28
Audit this contract →
← previous block·next block →recent activity