pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,828,953
← previous block
next block →
recent activity
Analyzing
Block #89,828,953
13 transactions · 10 stateful · 2026-07-24 05:05:11 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
#89,828,953
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
updateDataFeedsValuesPartial
#4
updatePrices
#5
0x5a5d9a99
#6
execFwdPositionOps
#7
0x3f5c179b
#8
0x3f5c179b
#9
execFwdPositionOps
#10
0x1fe271b4
· blocks 1
#12
setData
#11
handleOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
4 touches
1 conflict
0x0b92794d…48e4
0x0a2fbf…29b1
4 touches
1 conflict
0x0b92794d…48e5
0x0a2fbf…29b1
4 touches
1 conflict
0x0b92794d…48e8
0x0a2fbf…29b1
4 touches
1 conflict
0x55b4e430…44cb
0x754704…b603
4 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x085e35d2…8d20
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:
0x0a2fbf2d…f729b1
1 conflict on slot
0x0000000000…000006
Audit this contract →
← previous block
·
next block →
recent activity