pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,602,142
← previous block
next block →
recent activity
Analyzing
Block #85,602,142
12 transactions · 11 stateful · 2026-07-04 18:52:41 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,602,142
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
removeLiquidity
#2
0xab083028
#3
depositETH
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
forward
#7
0x6a4956f0
#8
setData
#9
exactInputSingle
#10
execOrders
· blocks 1
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7a1d036…b8aa
0x34b655…2a6f
4 touches
1 conflict
0xb3c96942…f0fc
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xef02ed46…48a4
0x34b655…2a6f
4 touches
1 conflict
0x329f2f7d…dcff
0x34b655…2a6f
4 touches
1 conflict
0x55a03051…2930
0x34b655…2a6f
4 touches
1 conflict
0x808f4007…2afb
0x34b655…2a6f
4 touches
1 conflict
0x3378e8b6…20a9
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:
Perpl
1 conflict on slot
0xa7a1d036b0…6eb8aa
Audit this contract →
← previous block
·
next block →
recent activity