pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,736,295
← previous block
next block →
recent activity
Analyzing
Block #89,736,295
13 transactions · 11 stateful · 2026-07-23 21:17:26 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,736,295
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
0x5a5d9a99
· blocks 1
#4
updateDataFeedsValuesPartial
#5
executeBatch
#6
batchUpdate
#8
forward
#9
claim
#10
0x6a62855e
#11
setData
#12
execOrders
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
4 touches
1 conflict
0xfaf3835b…98c7
0x34b655…2a6f
4 touches
1 conflict
0x4deeee1b…8c0c
0x34b655…2a6f
4 touches
1 conflict
0x1321736a…43e3
0x34b655…2a6f
2 touches
0 conflicts
0x29856edf…841b
0x34b655…2a6f
2 touches
0 conflicts
0x3c550c68…de2c
0x34b655…2a6f
2 touches
0 conflicts
0x4783345c…4a90
0x34b655…2a6f
2 touches
0 conflicts
0x6fe7d366…78ff
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
0x734ee32053…cecaae
Audit this contract →
← previous block
·
next block →
recent activity