← previous blocknext block →recent activity
Analyzing
Block #84,118,310
37 transactions · 21 stateful · 2026-06-27 22:02:21 UTC
Parallelism
86/100
Blocked
52%
Avg conflicts / tx
0.51
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,118,310 · 37 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
1w02w13w26w212w013w119w321w424w025w129w331w334w235w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d33d79a…5975
0xd32edf…ff58
9 touches
10 conflicts
0xab86573c…682e
0x34b655…2a6f
6 touches
3 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
6 touches
3 conflicts
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…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
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 0x6d33d79ad7…475975
Audit this contract →
← previous block·next block →recent activity