pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,736,544
← previous block
next block →
recent activity
Analyzing
Block #89,736,544
14 transactions · 13 stateful · 2026-07-23 21:18:42 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,736,544
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
0x5a5d9a99
· blocks 1
#5
execFwdPositionOps
#6
execFwdPositionOps
#7
executeBatch
#8
execFwdPositionOps
#9
updateDataFeedsValuesPartial
#10
updateDataFeedsValuesPartial
#11
0x6a6285aa
#12
setData
#13
execOrders
#4
0x5a5d9a99
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01b0ac5a…98c3
0x34b655…2a6f
2 touches
0 conflicts
0x10797f0b…439a
0x34b655…2a6f
2 touches
0 conflicts
0x206f4379…e08a
0x34b655…2a6f
2 touches
0 conflicts
0x2697123c…8526
0x34b655…2a6f
2 touches
0 conflicts
0x344425dc…71b4
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
0x6fe7d366be…a578ff
Audit this contract →
← previous block
·
next block →
recent activity