← previous blocknext block →recent activity
Analyzing
Block #95,007,351
24 transactions · 21 stateful · 2026-08-11 07:55:57 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,007,351 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w510w111w616w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ea72353…47a9
0xd32edf…ff58
13 touches
21 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0xce1dd8ab…9c7f
0x851145…3f07
6 touches
3 conflicts
0x11b69a7e…334e
0x01bff4…1071
6 touches
3 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
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
21 conflicts on slot 0x9ea72353b9…d947a9
Audit this contract →
← previous block·next block →recent activity