pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,700,483
← previous block
next block →
recent activity
Analyzing
Block #96,700,483
8 transactions · 6 stateful · 2026-08-17 06:08:14 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,700,483
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
execute
#3
updateDataFeedsValuesPartial
#4
setData
#5
execFwdPositionOpsV2
· blocks 1
#7
0x57368ddf
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6bdb9869…7558
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x0170241a…a745
0x34b655…2a6f
2 touches
0 conflicts
0x0313aedc…bfaf
0x34b655…2a6f
2 touches
0 conflicts
0x0313aedc…bfb0
0x34b655…2a6f
2 touches
0 conflicts
0x312c6e56…3d7a
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
0x6bdb9869c7…427558
Audit this contract →
← previous block
·
next block →
recent activity