pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,268,657
← previous block
next block →
recent activity
Analyzing
Block #96,268,657
9 transactions · 8 stateful · 2026-08-15 17:56:03 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,268,657
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrders
#3
0x5acec890
· blocks 1
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOpsV2
· blocks 1
#7
setData
#8
swapExactTokensForTokens
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2e1f5171…ad2d
0x34b655…2a6f
4 touches
1 conflict
0x73670e81…2813
0x34b655…2a6f
4 touches
1 conflict
0xe67c40ec…8793
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x0d119a2b…a7d7
0x34b655…2a6f
2 touches
0 conflicts
0x1c4fba23…39c4
0x34b655…2a6f
2 touches
0 conflicts
0x31616f97…1acc
0x34b655…2a6f
2 touches
0 conflicts
0x67209a5a…ab0e
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
0x2e1f517172…84ad2d
Audit this contract →
← previous block
·
next block →
recent activity