← previous blocknext block →recent activity
Analyzing
Block #84,112,500
33 transactions · 28 stateful · 2026-06-27 21:23:38 UTC
Parallelism
79/100
Blocked
54%
Avg conflicts / tx
1.36
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #84,112,500 · 33 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w38w010w118w219w320w421w522w624w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x21088e1e…0945
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…001d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
10 touches
10 conflicts
0x2d5c395b…6b5a
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 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
21 conflicts on slot 0x21088e1eb1…6c0945
Audit this contract →
← previous block·next block →recent activity