pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,880,895
← previous block
next block →
recent activity
Analyzing
Block #90,880,895
14 transactions · 9 stateful · 2026-07-27 21:37:51 UTC
Parallelism
86
/100
Blocked
11
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,880,895
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#2
execPerpOps
#3
execPerpOps
#4
updatePrices
#5
updatePrices
#6
updatePrices
#7
updatePrices
#8
0x5a5d9a99
#9
0x5a5d9a99
#10
updateDataFeedsValuesPartial
#12
execFwdPositionOps
#13
setData
#11
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0d488000…3831
0x34b655…2a6f
2 touches
0 conflicts
0x167de262…f61f
0x34b655…2a6f
2 touches
0 conflicts
0x206f4379…e08a
0x34b655…2a6f
2 touches
0 conflicts
0x2dfde2ed…8801
0x34b655…2a6f
2 touches
0 conflicts
0x2fade833…5de4
0x34b655…2a6f
2 touches
0 conflicts
0x5e8f1436…53a6
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity