pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,580,977
← previous block
next block →
recent activity
Analyzing
Block #95,580,977
12 transactions · 10 stateful · 2026-08-13 08:15:37 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,580,977
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
0x5acec890
#6
setData
#7
execFwdPositionOps
#8
0x6a7d7da1
#9
proposeResolution
#10
withdraw
#11
0x59558d29
#2
matchOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcbcfed5b…96a6
0x754704…b603
4 touches
1 conflict
0x50be7f5d…2a30
0x754704…b603
4 touches
1 conflict
0x9feedc78…da4a
0x754704…b603
4 touches
1 conflict
0x038b9243…553d
0x34b655…2a6f
2 touches
0 conflicts
0x17091c69…e7f3
0x34b655…2a6f
2 touches
0 conflicts
0x42b10c57…3ee7
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
2 touches
0 conflicts
0x0fc41e7b…6831
0x98dc6e…8633
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:
USDC (USDC)
1 conflict on slot
0xcbcfed5bf3…4496a6
Audit this contract →
← previous block
·
next block →
recent activity