pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,687,890
← previous block
next block →
recent activity
Analyzing
Block #89,687,890
9 transactions · 8 stateful · 2026-07-23 17:13:13 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,687,890
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
#7
0x36f359b0
#8
setData
#5
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0efc210e…70ab
0x34b655…2a6f
4 touches
1 conflict
0x08636046…e60f
0x34b655…2a6f
4 touches
1 conflict
0xd4305f3b…7f3d
0x34b655…2a6f
4 touches
1 conflict
0x5ee06fae…07bf
0x34b655…2a6f
3 touches
1 conflict
0x51028c5e…235c
0x34b655…2a6f
2 touches
0 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
2 touches
0 conflicts
0xa9d5be35…1cb9
0x34b655…2a6f
2 touches
0 conflicts
0xd0f6f4f2…dffa
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
0x0efc210ee8…0e70ab
Audit this contract →
← previous block
·
next block →
recent activity