pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,672,779
← previous block
next block →
recent activity
Analyzing
Block #86,672,779
25 transactions · 23 stateful · 2026-07-09 18:01:07 UTC
Parallelism
80
/100
Blocked
35
%
Avg conflicts / tx
0.68
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,672,779
· 25 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x5a5d9a99
· blocks 5
#7
execFwdPositionOps
· blocks 1
#8
execFwdPositionOps
· blocks 1
#9
updateDataFeedsValuesPartial
#10
updateDataFeedsValuesPartial
#13
forward
#14
batchUpdate
#16
execFwdPositionOps
#17
0x6a4fe25b
#18
setData
#19
0xa7e14e…6370
#20
0xab92a6…544f
#21
execOrders
· blocks 1
#22
execOrders
#24
0xc7e3ec2c
#3
0x5a5d9a99
· blocks 4
#11
execFwdPositionOps
#12
0xed82b078
#15
execFwdPositionOps
#4
0x5a5d9a99
· blocks 3
#5
0x5a5d9a99
· blocks 1
#23
execOrders
#6
0x5a5d9a99
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
4
w2
5
w3
6
w4
7
w0
8
w0
11
w1
12
w1
15
w1
21
w0
23
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1a9
0xb1dbf0…c0d3
10 touches
10 conflicts
0x8a35acfb…d1aa
0xb1dbf0…c0d3
9 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x44429a9b…771d
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0x1b16f7bf…6e06
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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:
0xb1dbf05f…b1c0d3
10 conflicts on slot
0x8a35acfbc1…6bd1a9
Audit this contract →
← previous block
·
next block →
recent activity