← previous blocknext block →recent activity
Analyzing
Block #84,191,944
30 transactions · 27 stateful · 2026-06-28 06:12:20 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,191,944 · 30 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
1w02w13w26w310w011w114w317w018w121w423w227w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa50c3616…c6fd
0xd32edf…ff58
7 touches
6 conflicts
0xd5b10148…e637
0x1b6862…e19c
6 touches
3 conflicts
0xe75cebb6…6b36
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…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
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
6 conflicts on slot 0xa50c361655…f0c6fd
Audit this contract →
← previous block·next block →recent activity