← previous blocknext block →recent activity
Analyzing
Block #84,460,332
50 transactions · 35 stateful · 2026-06-29 12:00:59 UTC
Parallelism
84/100
Blocked
66%
Avg conflicts / tx
1.16
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,460,332 · 50 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
1w02w17w110w111w231w332w433w534w635w737w338w239w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6716f66…b4d1
0xd32edf…ff58
15 touches
28 conflicts
0x56785e37…a197
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0x93afca4c…b47c
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
28 conflicts on slot 0xb6716f664d…e8b4d1
Audit this contract →
← previous block·next block →recent activity