pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,351,664
← previous block
next block →
recent activity
Analyzing
Block #95,351,664
12 transactions · 9 stateful · 2026-08-12 12:59:53 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,351,664
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#6
forward
#7
setData
#8
0x343aab…900c
#9
0x7ddeb9…8aa1
#10
0x2ec5d0…727b
#11
0x59558d29
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36e7818c…c2ea
0x34b655…2a6f
4 touches
1 conflict
0x83da2486…8024
0x34b655…2a6f
4 touches
1 conflict
0x99c00c45…c701
0x34b655…2a6f
4 touches
1 conflict
0x31fd9aa9…e0fc
0x34b655…2a6f
4 touches
1 conflict
0x155e52ca…fac7
0x34b655…2a6f
2 touches
0 conflicts
0x216ffe66…1f94
0x34b655…2a6f
2 touches
0 conflicts
0x2860b9bb…282c
0x34b655…2a6f
2 touches
0 conflicts
0x4f394483…ff62
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
0x36e7818c21…19c2ea
Audit this contract →
← previous block
·
next block →
recent activity