← previous blocknext block →recent activity
Analyzing
Block #85,848,413
30 transactions · 23 stateful · 2026-07-05 22:13:48 UTC
Parallelism
73/100
Blocked
52%
Avg conflicts / tx
1.23
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,848,413 · 30 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w516w621w725w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5a3d68d…2007
0xd32edf…ff58
15 touches
28 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x9075b077…87d1
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
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
28 conflicts on slot 0xb5a3d68de5…5f2007
Audit this contract →
← previous block·next block →recent activity