pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,798,089
← previous block
next block →
recent activity
Analyzing
Block #95,798,089
9 transactions · 8 stateful · 2026-08-14 02:28:41 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,798,089
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x000000b2
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOpsV2
· blocks 1
#5
0x3f5c179b
· blocks 1
#8
setData
#6
execFwdPositionOpsV2
#7
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e733b13…b909
0x851145…3f07
4 touches
1 conflict
0xf51ec09c…b4a9
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x0cdc38ed…c280
0x34b655…2a6f
4 touches
1 conflict
0x109d8a52…a7b7
0x34b655…2a6f
4 touches
1 conflict
0x323c81b3…7850
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4c619b7d…f4fa
0x34b655…2a6f
4 touches
1 conflict
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:
0x851145ea…9f3f07
1 conflict on slot
0x6e733b13d5…d4b909
Audit this contract →
← previous block
·
next block →
recent activity