pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,285,027
← previous block
next block →
recent activity
Analyzing
Block #91,285,027
12 transactions · 11 stateful · 2026-07-29 07:32:41 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,285,027
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
0x5a5d9a99
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#6
execFwdPositionOps
#7
0x57368ddf
#8
execOrders
#9
0x6a69ad10
#10
setData
#11
0xc7e3ec2c
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xefcdf197…96a2
0x34b655…2a6f
4 touches
1 conflict
0x35bdd2fa…c789
0x158622…375e
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x0147158c…f0a8
0x34b655…2a6f
2 touches
0 conflicts
0x016fd28a…a1fc
0x34b655…2a6f
2 touches
0 conflicts
0x0a57e70b…80eb
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
0x7aad02c682…feb979
Audit this contract →
← previous block
·
next block →
recent activity