← previous blocknext block →recent activity
Analyzing
Block #86,328,908
22 transactions · 21 stateful · 2026-07-08 03:40:28 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,328,908 · 22 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
1w02w13w24w38w09w111w412w214w015w120w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdcd5fce4…eb3f
0xd32edf…ff58
9 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x4bfdcd51…9b58
0x34b655…2a6f
4 touches
1 conflict
0xa33e4ca4…e6c7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x6b405d1c…29a4
0x851145…3f07
4 touches
1 conflict
0x00000000…0012
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 0xdcd5fce40e…57eb3f
Audit this contract →
← previous block·next block →recent activity