← previous blocknext block →recent activity
Analyzing
Block #86,273,379
28 transactions · 24 stateful · 2026-07-07 21:29:40 UTC
Parallelism
82/100
Blocked
50%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,273,379 · 28 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
1w02w13w27w311w012w114w315w016w217w219w420w321w123w227w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x671fcb60…64f8
0xd32edf…ff58
9 touches
10 conflicts
0x27a04273…27c5
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x4681609f…6493
0x34b655…2a6f
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
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 0x671fcb60c7…2e64f8
Audit this contract →
← previous block·next block →recent activity