pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,587,188
← previous block
next block →
recent activity
Analyzing
Block #95,587,188
11 transactions · 10 stateful · 2026-08-13 08:46:51 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,587,188
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#7
0x29eed2d3
#8
0x6a7d84f3
#9
setData
#10
0x59558d29
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x84d74093…7808
0x34b655…2a6f
4 touches
1 conflict
0x0227484c…b688
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x0227484c…b689
0x34b655…2a6f
4 touches
1 conflict
0x67724a34…a7a5
0x34b655…2a6f
4 touches
1 conflict
0x42acbf95…eec3
0x34b655…2a6f
4 touches
1 conflict
0x74d4bec8…70d8
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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:
Perpl
1 conflict on slot
0x84d74093a5…ec7808
Audit this contract →
← previous block
·
next block →
recent activity