pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,518,753
← previous block
next block →
recent activity
Analyzing
Block #89,518,753
11 transactions · 10 stateful · 2026-07-22 23:13:28 UTC
Parallelism
82
/100
Blocked
30
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,518,753
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 3
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
executeBatch
#6
batchUpdate
#8
0x6a614f10
#9
setData
#2
execFwdPositionOps
#7
execFwdPositionOps
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x574628e9…dcc3
0x34b655…2a6f
4 touches
1 conflict
0x7b1050dc…1104
0x34b655…2a6f
4 touches
1 conflict
0xa242e227…2e45
0x34b655…2a6f
4 touches
1 conflict
0xaf19c45c…d1a9
0x34b655…2a6f
4 touches
1 conflict
0xeb403811…08ce
0x34b655…2a6f
4 touches
1 conflict
0x20cb8909…c6c3
0x34b655…2a6f
2 touches
0 conflicts
0x2477d0da…f68e
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
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity