pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,809,519
← previous block
next block →
recent activity
Analyzing
Block #86,809,519
10 transactions · 9 stateful · 2026-07-10 09:14:15 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,809,519
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePosition
#3
0x3f5c179b
#4
batchUpdate
#5
execFwdPositionOps
· blocks 1
#7
setData
#8
execOrders
#9
0xc7e3ec2c
#6
execFwdPositionOps
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
0xc40c8e2b…b832
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xa27fa22d…7dca
0x54cd53…9e7d
2 touches
0 conflicts
0x20d190fe…bb36
0x6657d1…8ccc
2 touches
0 conflicts
0x3bac75e5…8172
0x6657d1…8ccc
2 touches
0 conflicts
0x3d315ed7…c817
0x6657d1…8ccc
2 touches
0 conflicts
0x3d42678f…3cc1
0x6657d1…8ccc
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
0xc40c8e2bad…1fb832
Audit this contract →
← previous block
·
next block →
recent activity