← previous blocknext block →recent activity
Analyzing
Block #95,005,795
22 transactions · 18 stateful · 2026-08-11 07:48:06 UTC
Parallelism
77/100
Blocked
61%
Avg conflicts / tx
1.18
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,005,795 · 22 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
1w02w13w24w36w08w010w111w412w113w214w316w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2030b32…b192
0xd32edf…ff58
9 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xc70dd80f…d075
0x34b655…2a6f
6 touches
3 conflicts
0x0db691ab…3ee3
0x34b655…2a6f
4 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0xbdac1450…8264
0x065c9d…c394
4 touches
1 conflict
0x0778475b…bd75
0x2a68ba…90c5
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 0xe2030b32b4…feb192
Audit this contract →
← previous block·next block →recent activity