← previous blocknext block →recent activity
Analyzing
Block #95,022,183
25 transactions · 21 stateful · 2026-08-11 09:10:34 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,022,183 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w19w210w311w414w015w116w217w318w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf7610d3…d837
0xd32edf…ff58
9 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x46cb45de…a568
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
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
10 conflicts on slot 0xcf7610d34c…d4d837
Audit this contract →
← previous block·next block →recent activity