pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,720,784
← previous block
next block →
recent activity
Analyzing
Block #95,720,784
9 transactions · 8 stateful · 2026-08-13 19:59:53 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,720,784
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOpsV2
· blocks 1
#4
0x3f5c179b
#5
0x3f5c179b
#7
setData
· blocks 1
#6
execFwdPositionOpsV2
#8
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0db691ab…3ee3
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x6bf457e3…9576
0x34b655…2a6f
4 touches
1 conflict
0x33f54bd6…9ac3
0x34b655…2a6f
4 touches
1 conflict
0xa03c2a35…52e6
0x34b655…2a6f
4 touches
1 conflict
0x3aae83ca…8cc1
0x34b655…2a6f
4 touches
1 conflict
0x713ba679…f953
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
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
0x0db691abac…993ee3
Audit this contract →
← previous block
·
next block →
recent activity