pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,744,412
← previous block
next block →
recent activity
Analyzing
Block #89,744,412
10 transactions · 10 stateful · 2026-07-23 21:58:29 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,744,412
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
removeLiquidity
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
· blocks 1
#7
forward
#8
setData
#9
execOrders
#4
execFwdPositionOps
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4c56761…79e0
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0x1fef02…8963
2 touches
0 conflicts
0x704ea88c…d5be
0x1fef02…8963
2 touches
0 conflicts
0x745c4454…a6ce
0x1fef02…8963
2 touches
0 conflicts
0x0ddfdaf2…9e00
0x34b655…2a6f
2 touches
0 conflicts
0x327c57dd…836d
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
0xa4c56761b7…2c79e0
Audit this contract →
← previous block
·
next block →
recent activity