← previous blocknext block →recent activity
Analyzing
Block #79,407,094
25 transactions · 22 stateful · 2026-06-06 02:03:48 UTC
Parallelism
76/100
Blocked
59%
Avg conflicts / tx
1.32
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #79,407,094 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w49w510w311w312w413w516w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f1e5d5b…70b2
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xc13fac9b…d2d5
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x5540f956…69e8
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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
15 conflicts on slot 0x7f1e5d5b0b…fd70b2
Audit this contract →
← previous block·next block →recent activity