pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,371,025
← previous block
next block →
recent activity
Analyzing
Block #85,371,025
11 transactions · 9 stateful · 2026-07-03 17:13:45 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,371,025
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execPerpOps
#3
0x5a5d9a99
· blocks 1
#5
execFwdPositionOps
#6
0x3f5c179b
#7
0x3f5c179b
#8
0xed82b078
#9
setData
#10
0x065878…9375
#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
0x08e8f2c9…a11a
0x34b655…2a6f
4 touches
1 conflict
0xcef70a96…db44
0x34b655…2a6f
4 touches
1 conflict
0x342a12bc…c045
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x3230277c…ef39
0xc8689a…ee79
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
2 touches
0 conflicts
0x35003bda…a553
0x34b655…2a6f
2 touches
0 conflicts
0x526cc620…bd45
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
0x08e8f2c94d…1ca11a
Audit this contract →
← previous block
·
next block →
recent activity