pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,507,924
← previous block
next block →
recent activity
Analyzing
Block #96,507,924
10 transactions · 8 stateful · 2026-08-16 13:59:46 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,507,924
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5acec890
#3
updateDataFeedsValuesPartial
#4
0xc9623387
#5
exactInputSingle
#6
execFwdPositionOpsV2
· blocks 2
#9
setData
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26607bc2…7fd6
0x34b655…2a6f
4 touches
1 conflict
0x85e59464…9104
0x34b655…2a6f
4 touches
1 conflict
0xab981df1…2941
0x34b655…2a6f
4 touches
1 conflict
0xef048f92…572b
0x34b655…2a6f
4 touches
1 conflict
0x16e75abd…f3ad
0x34b655…2a6f
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
0x26607bc28d…b87fd6
Audit this contract →
← previous block
·
next block →
recent activity