pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,733,899
← previous block
next block →
recent activity
Analyzing
Block #86,733,899
11 transactions · 9 stateful · 2026-07-10 00:49:10 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,733,899
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#5
batchUpdate
#6
0x0cf032c6
#7
setData
#8
0x749b6e…93cf
#9
execOrders
· blocks 1
#4
execFwdPositionOps
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef7cdebf…b33b
0x34b655…2a6f
4 touches
1 conflict
0x9accd401…78db
0x34b655…2a6f
4 touches
1 conflict
0xd6aabe89…92f5
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe3766636…4a66
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x0d43cc69…6f83
0x34b655…2a6f
4 touches
1 conflict
0x1353affc…75e0
0x34b655…2a6f
4 touches
1 conflict
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
0xef7cdebfc1…cab33b
Audit this contract →
← previous block
·
next block →
recent activity