pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,247,430
← previous block
next block →
recent activity
Analyzing
Block #86,247,430
13 transactions · 10 stateful · 2026-07-07 18:36:27 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,247,430
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xe3a3c9cc
#2
updateDataFeedsValuesPartial
#3
updatePrices
#4
execOrders
#5
execOrders
· blocks 1
#6
execFwdPositionOps
#8
0x6a4d47a3
#9
setData
#10
execOrders
#11
execOrders
#12
execOrders
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7fcd31f6…cafb
0x34b655…2a6f
4 touches
1 conflict
0xd800e635…b1d7
0x34b655…2a6f
4 touches
1 conflict
0x3bdd71a2…b6eb
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
2 touches
0 conflicts
0x461d2e7f…cc22
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
0x34b655…2a6f
2 touches
0 conflicts
0x8cc1393f…07fb
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
0x7fcd31f681…12cafb
Audit this contract →
← previous block
·
next block →
recent activity