← previous blocknext block →recent activity
Analyzing
Block #84,334,168
42 transactions · 34 stateful · 2026-06-28 22:00:03 UTC
Parallelism
88/100
Blocked
35%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,334,168 · 42 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
1w03w08w09w113w120w221w322w423w024w125w226w327w028w129w137w038w139w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd39f684…dad9
0xd32edf…ff58
9 touches
10 conflicts
0xf79df061…e005
0xe52b14…7230
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x56785e37…a197
0x065c9d…c394
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
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 0xbd39f68417…1edad9
Audit this contract →
← previous block·next block →recent activity