pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,405,163
← previous block
next block →
recent activity
Analyzing
Block #95,405,163
11 transactions · 10 stateful · 2026-08-12 17:30:46 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,405,163
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
0xab083028
#3
execOrder
· blocks 1
#4
execPerpOps
#6
execFwdPositionOps
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
updateTemporalNumericValuesV1
#10
setData
#5
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cabb80a…46bf
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xf29db88e…d471
0x34b655…2a6f
4 touches
1 conflict
0x007b42ba…13dc
0x34b655…2a6f
2 touches
0 conflicts
0x0147a069…7a58
0x34b655…2a6f
2 touches
0 conflicts
0x0344fc81…41ce
0x34b655…2a6f
2 touches
0 conflicts
0x057c4f35…9bfb
0x34b655…2a6f
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
0x4cabb80a0e…7546bf
Audit this contract →
← previous block
·
next block →
recent activity