pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,135,320
← previous block
next block →
recent activity
Analyzing
Block #96,135,320
9 transactions · 7 stateful · 2026-08-15 06:45:26 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,135,320
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x148731…4e99
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x5acec890
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
· blocks 1
#8
setData
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xa366fc53…ed2a
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0b1a9431…183e
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
0x34b655…2a6f
2 touches
0 conflicts
0x78860c4f…cade
0x34b655…2a6f
2 touches
0 conflicts
0x9fdaa3fd…4066
0x34b655…2a6f
2 touches
0 conflicts
0xa2e89145…7dfa
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
0x66bdb4c268…a97ea6
Audit this contract →
← previous block
·
next block →
recent activity