pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,727,852
← previous block
next block →
recent activity
Analyzing
Block #95,727,852
10 transactions · 9 stateful · 2026-08-13 20:35:26 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,727,852
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execOrders
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOpsV2
#5
updateTemporalNumericValuesV1
#6
0x6a7e2b06
#7
setData
#8
0x9a1b6022
· blocks 1
#9
0x9a1b6022
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x472511a8…d576
0x0a4fcb…a602
4 touches
1 conflict
0x472511a8…d575
0x0a4fcb…a602
4 touches
1 conflict
0x92422ced…8761
0x754704…b603
4 touches
1 conflict
0xb8bd6b97…08a2
0x754704…b603
4 touches
1 conflict
0x23a5a162…b791
0x065c9d…c394
2 touches
0 conflicts
0x508663a3…78cb
0x065c9d…c394
2 touches
0 conflicts
0x72195e54…6ba1
0x065c9d…c394
2 touches
0 conflicts
0x7878e773…bad1
0x065c9d…c394
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:
0x0a4fcba9…7ba602
1 conflict on slot
0x472511a828…1bd576
Audit this contract →
← previous block
·
next block →
recent activity