pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,405,656
← previous block
next block →
recent activity
Analyzing
Block #89,405,656
12 transactions · 10 stateful · 2026-07-22 10:37:49 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,405,656
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
0x5a5d9a99
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#6
execFwdPositionOps
· blocks 1
#8
0x3f5c179b
#9
0x0c7abd22
#10
batchUpdate
#11
setData
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8212e232…180d
0x34b655…2a6f
4 touches
1 conflict
0x8212e232…180e
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9cbe5c47…424b
0x34b655…2a6f
4 touches
1 conflict
0xa09be165…16b9
0x34b655…2a6f
4 touches
1 conflict
0xf94d916b…d599
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x346e6e22…8deb
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
0x8212e232c3…3f180d
Audit this contract →
← previous block
·
next block →
recent activity