pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,568,585
← previous block
next block →
recent activity
Analyzing
Block #95,568,585
10 transactions · 9 stateful · 2026-08-13 07:13:18 UTC
Parallelism
60
/100
Blocked
33
%
Avg conflicts / tx
0.4
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,568,585
· 10 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
execOrder
· blocks 2
#4
updateDataFeedsValuesPartial
#5
0x3f5c179b
#6
execFwdPositionOps
#8
multicall
#9
execOrders
#2
execOrder
· blocks 1
#3
0x5acec890
· blocks 1
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
7
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2840c278…bbc7
0x34b655…2a6f
6 touches
3 conflicts
0xaae6463e…bfcc
0x34b655…2a6f
4 touches
1 conflict
0x203f132b…89fc
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x312e7bb3…b9b4
0x34b655…2a6f
2 touches
0 conflicts
0x35649443…8b45
0x34b655…2a6f
2 touches
0 conflicts
0x5e78c401…7a7e
0x34b655…2a6f
2 touches
0 conflicts
0x8cff5807…0f05
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
3 conflicts on slot
0x2840c278a3…01bbc7
Audit this contract →
← previous block
·
next block →
recent activity