pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,692,079
← previous block
next block →
recent activity
Analyzing
Block #87,692,079
10 transactions · 9 stateful · 2026-07-14 11:35:55 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
#87,692,079
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
0x5a5d9a99
#3
execFwdPositionOps
· blocks 1
#5
0x57368ddf
#6
execFwdPositionOps
#7
updateDataFeedsValuesPartial
#8
commit
#9
setData
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec653969…3e38
0x34b655…2a6f
4 touches
1 conflict
0xec653969…3e39
0x34b655…2a6f
4 touches
1 conflict
0x3b80f5b2…72ad
0x34b655…2a6f
4 touches
1 conflict
0x177f8108…ff11
0x34b655…2a6f
4 touches
1 conflict
0xe8587278…40f5
0x34b655…2a6f
4 touches
1 conflict
0x1cc14d91…6d34
0x34b655…2a6f
3 touches
1 conflict
0x15bb0662…b802
0x34b655…2a6f
2 touches
0 conflicts
0x2fdfa032…139c
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
0xec653969b5…af3e38
Audit this contract →
← previous block
·
next block →
recent activity