pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,526,545
← previous block
next block →
recent activity
Analyzing
Block #89,526,545
9 transactions · 9 stateful · 2026-07-23 00:05:35 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,526,545
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#5
updatePriceFeedsIfNecessary
#7
0x6a615b46
#8
setData
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9210e826…1414
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xde95b18d…3751
0x34b655…2a6f
4 touches
1 conflict
0x3e32e465…31cc
0x34b655…2a6f
4 touches
1 conflict
0xfef0ce0a…aa7f
0x34b655…2a6f
4 touches
1 conflict
0x52e83d2a…813a
0x34b655…2a6f
4 touches
1 conflict
0x1bb56de3…732e
0x34b655…2a6f
4 touches
1 conflict
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
0x9210e826c8…c41414
Audit this contract →
← previous block
·
next block →
recent activity