← previous blocknext block →recent activity
Analyzing
Block #86,387,168
40 transactions · 30 stateful · 2026-07-08 10:09:47 UTC
Parallelism
80/100
Blocked
73%
Avg conflicts / tx
1.2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,387,168 · 40 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
1w02w13w24w15w26w317w318w419w520w621w225w331w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x29c48dc3…28b2
0xd32edf…ff58
13 touches
21 conflicts
0xe5060fe3…ebe5
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
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
21 conflicts on slot 0x29c48dc35e…9128b2
Audit this contract →
← previous block·next block →recent activity