pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,814,941
← previous block
next block →
recent activity
Analyzing
Block #94,814,941
9 transactions · 8 stateful · 2026-08-10 15:48:10 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,814,941
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execPerpOps
#3
execPerpOps
#4
execFwdPositionOps
· blocks 2
#7
0x3f5c179b
#8
setData
#5
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x772ab420…c2f6
0x34b655…2a6f
6 touches
3 conflicts
0x66532680…4feb
0x34b655…2a6f
4 touches
1 conflict
0x0189810e…848a
0x34b655…2a6f
4 touches
1 conflict
0x143556cd…07a5
0x34b655…2a6f
2 touches
0 conflicts
0x28225554…5bde
0x34b655…2a6f
2 touches
0 conflicts
0x57fa2ee5…eec6
0x34b655…2a6f
2 touches
0 conflicts
0x6af385b8…971b
0x34b655…2a6f
2 touches
0 conflicts
0x6af385b8…971c
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
3 conflicts on slot
0x772ab420dc…dcc2f6
Audit this contract →
← previous block
·
next block →
recent activity