pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,173,905
← previous block
next block →
recent activity
Analyzing
Block #92,173,905
11 transactions · 9 stateful · 2026-08-01 10:05:34 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,173,905
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
execPerpOps
#3
execPerpOps
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 1
#6
setData
#7
updatePriceFeedsIfNecessary
#8
claimRewards
#10
execFwdPositionOps
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0efc210e…70ab
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x0c0e0a78…c532
0x34b655…2a6f
2 touches
0 conflicts
0x23769ebc…c8ed
0x34b655…2a6f
2 touches
0 conflicts
0x248e43aa…7287
0x34b655…2a6f
2 touches
0 conflicts
0x2cf0b050…20d8
0x34b655…2a6f
2 touches
0 conflicts
0x35a9f06c…7689
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