pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,576,522
← previous block
next block →
recent activity
Analyzing
Block #89,576,522
9 transactions · 9 stateful · 2026-07-23 05:39:21 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,576,522
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
#5
0x57368ddf
#6
execFwdPositionOps
#7
setData
#8
execOrders
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc30234e3…c8fe
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xc9e07b63…930d
0x34b655…2a6f
4 touches
1 conflict
0x59f08f52…6487
0x34b655…2a6f
4 touches
1 conflict
0x60dc7b78…d1d5
0x34b655…2a6f
4 touches
1 conflict
0x6bf71f68…fd07
0x34b655…2a6f
4 touches
1 conflict
0x796c1a47…2bfb
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
0xc30234e362…80c8fe
Audit this contract →
← previous block
·
next block →
recent activity