← previous blocknext block →recent activity
Analyzing
Block #85,855,441
32 transactions · 27 stateful · 2026-07-05 23:00:38 UTC
Parallelism
66/100
Blocked
48%
Avg conflicts / tx
1.34
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #85,855,441 · 32 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31bfcb7a…ce13
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x93afca4c…b478
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
36 conflicts on slot 0x31bfcb7a3b…65ce13
Audit this contract →
← previous block·next block →recent activity