pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,568,066
← previous block
next block →
recent activity
Analyzing
Block #96,568,066
10 transactions · 8 stateful · 2026-08-16 19:02:14 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,568,066
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0x5acec890
#3
execOrders
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOpsV2
· blocks 1
#6
forward
#8
setData
#9
0x785f5745
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeeb46b9e…93e1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x481b500f…7ef3
0x34b655…2a6f
4 touches
1 conflict
0x03c38bff…f48f
0x34b655…2a6f
2 touches
0 conflicts
0x054afe69…16e8
0x34b655…2a6f
2 touches
0 conflicts
0x0eb3ab36…88b9
0x34b655…2a6f
2 touches
0 conflicts
0x0eb3ab36…88ba
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
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
0xeeb46b9e75…ed93e1
Audit this contract →
← previous block
·
next block →
recent activity