← previous blocknext block →recent activity
Analyzing
Block #84,559,883
33 transactions · 23 stateful · 2026-06-29 23:05:29 UTC
Parallelism
85/100
Blocked
39%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,559,883 · 33 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
1w02w13w214w016w318w421w223w024w128w330w131w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42be0611…dbcc
0xd32edf…ff58
9 touches
10 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
6 touches
3 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
6 touches
3 conflicts
0x52163873…f09f
0x34b655…2a6f
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
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 0x42be06118b…73dbcc
Audit this contract →
← previous block·next block →recent activity