← previous blocknext block →recent activity
Analyzing
Block #83,631,392
25 transactions · 22 stateful · 2026-06-25 15:55:39 UTC
Parallelism
80/100
Blocked
41%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,631,392 · 25 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
1w02w13w25w06w17w08w110w311w012w116w018w420w123w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5d0b2fb…e69f
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0xd59f6ed1…03e7
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 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
10 conflicts on slot 0xf5d0b2fb64…fce69f
Audit this contract →
← previous block·next block →recent activity