pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,714,156
← previous block
next block →
recent activity
Analyzing
Block #95,714,156
8 transactions · 6 stateful · 2026-08-13 19:26:28 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,714,156
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePosition
#3
execFwdPositionOpsV2
· blocks 1
#4
0x57368ddf
#6
0xd708c5d8
#7
setData
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd96f96f…5843
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa27fa22d…7dca
0x54cd53…9e7d
2 touches
0 conflicts
0x25d7dfcf…296e
0x6657d1…8ccc
2 touches
0 conflicts
0x43a6f469…63a2
0x6657d1…8ccc
2 touches
0 conflicts
0x48f186b1…4c28
0x6657d1…8ccc
2 touches
0 conflicts
0x54ed2fa7…6ff4
0x6657d1…8ccc
2 touches
0 conflicts
0x5edd1dec…930a
0x6657d1…8ccc
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
0xbd96f96f0a…875843
Audit this contract →
← previous block
·
next block →
recent activity