← previous blocknext block →recent activity
Analyzing
Block #85,532,397
14 transactions · 13 stateful · 2026-07-04 11:08:06 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,532,397 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w28w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd05c0ae1…4453
0xd32edf…ff58
5 touches
3 conflicts
0x39bc282c…5708
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x50a32a96…1db5
0x065c9d…c394
4 touches
1 conflict
0x95fda418…36d4
0x065c9d…c394
3 touches
1 conflict
0x4d70c11b…26d6
0x065c9d…c394
3 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
2 touches
0 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
3 conflicts on slot 0xd05c0ae1f4…054453
Audit this contract →
← previous block·next block →recent activity