← previous blocknext block →recent activity
Analyzing
Block #86,082,141
30 transactions · 25 stateful · 2026-07-07 00:12:50 UTC
Parallelism
83/100
Blocked
28%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,082,141 · 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
1w03w15w06w17w210w219w321w022w424w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda5dc526…2a95
0xd32edf…ff58
7 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0xd025d7d7…f05a
0x3bd359…433a
4 touches
1 conflict
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa1f84d6b…8066
0x065c9d…c394
3 touches
1 conflict
0x2424001d…1ab0
0x065c9d…c394
3 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
6 conflicts on slot 0xda5dc52687…702a95
Audit this contract →
← previous block·next block →recent activity