← previous blocknext block →recent activity
Analyzing
Block #85,913,867
38 transactions · 32 stateful · 2026-07-06 05:29:45 UTC
Parallelism
87/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,913,867 · 38 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
1w02w13w24w05w06w17w08w110w214w320w124w026w429w433w134w235w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe4e43a7…d10d
0xd32edf…ff58
7 touches
6 conflicts
0x160f117d…8e90
0x065c9d…c394
6 touches
3 conflicts
0xb33ff823…1188
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…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0029
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 0xbe4e43a7c6…0cd10d
Audit this contract →
← previous block·next block →recent activity