← previous blocknext block →recent activity
Analyzing
Block #79,249,971
36 transactions · 23 stateful · 2026-06-05 08:32:32 UTC
Parallelism
86/100
Blocked
39%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #79,249,971 · 36 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
1w02w13w25w16w09w011w113w219w320w428w133w034w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5eddb920…f26d
0xd32edf…ff58
9 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
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 0x5eddb920c8…85f26d
Audit this contract →
← previous block·next block →recent activity