pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,304,854
← previous block
next block →
recent activity
Analyzing
Block #96,304,854
9 transactions · 7 stateful · 2026-08-15 20:58:07 UTC
Parallelism
78
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,304,854
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOpsV2
· blocks 2
#4
execFwdPositionOpsV2
#5
updateDataFeedsValuesPartial
#6
updateTemporalNumericValuesV1
#7
setData
#8
0x61d59c2d
#2
execFwdPositionOpsV2
#3
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xa5a8ffca…8de2
0x34b655…2a6f
4 touches
1 conflict
0x08e8f2c9…a11a
0x34b655…2a6f
2 touches
0 conflicts
0x0db691ab…3ee3
0x34b655…2a6f
2 touches
0 conflicts
0x187e8dfa…28e2
0x34b655…2a6f
2 touches
0 conflicts
0x2170bea4…4722
0x34b655…2a6f
2 touches
0 conflicts
0x2170bea4…4723
0x34b655…2a6f
2 touches
0 conflicts
0x287036c6…a278
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
0x0000000000…0000c9
Audit this contract →
← previous block
·
next block →
recent activity