← previous blocknext block →recent activity
Analyzing
Block #95,370,233
20 transactions · 18 stateful · 2026-08-12 14:33:56 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,370,233 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w18w49w010w111w512w014w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec5ba06b…72eb
0xd32edf…ff58
11 touches
15 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xed42047f…2109
0x065c9d…c394
5 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0x4d42f16e…a6cc
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
15 conflicts on slot 0xec5ba06be5…e272eb
Audit this contract →
← previous block·next block →recent activity