pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,758,485
← previous block
next block →
recent activity
Analyzing
Block #95,758,485
8 transactions · 8 stateful · 2026-08-13 23:09:30 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,758,485
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
postStateList
#2
updatePrices
#3
execFwdPositionOpsV2
· blocks 1
#4
updateDataFeedsValuesPartial
#5
forward
#7
setData
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe64d2555…8caf
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xba1edffb…323e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x13d12d78…4c97
0x34b655…2a6f
2 touches
0 conflicts
0x1d2affc9…7d67
0x34b655…2a6f
2 touches
0 conflicts
0x2c7064fa…682d
0x34b655…2a6f
2 touches
0 conflicts
0x4acc6dca…a868
0x34b655…2a6f
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
0xe64d255503…c58caf
Audit this contract →
← previous block
·
next block →
recent activity