pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,367,594
← previous block
next block →
recent activity
Analyzing
Block #86,367,594
11 transactions · 10 stateful · 2026-07-08 07:58:38 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,367,594
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0xab083028
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x62be7533
#6
execFwdPositionOps
#8
0x6a4e03a6
#9
setData
#10
0xc7e3ec2c
#7
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ae937bf…d47d
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0000
0x16d564…365f
2 touches
0 conflicts
0x00000000…0001
0x16d564…365f
2 touches
0 conflicts
0x00000000…0008
0x16d564…365f
2 touches
0 conflicts
0x99f666e3…b2a2
0x3bd359…433a
2 touches
0 conflicts
0xa3f33f3e…804f
0x3bd359…433a
2 touches
0 conflicts
0xd5e7b01d…7f76
0x3bd359…433a
2 touches
0 conflicts
0x06d6cdab…0c00
0x754704…b603
2 touches
0 conflicts
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
1 conflict on slot
0x9ae937bfe0…00d47d
Audit this contract →
← previous block
·
next block →
recent activity