pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,331,044
← previous block
next block →
recent activity
Analyzing
Block #84,331,044
9 transactions · 7 stateful · 2026-06-28 21:39:17 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,331,044
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0xa96df62f
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 1
#7
setData
#8
0xc7e3ec2c
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2941131f…cfd2
0x34b655…2a6f
4 touches
1 conflict
0xd2cdfa3f…f071
0x34b655…2a6f
4 touches
1 conflict
0x08cc68a2…2a59
0x34b655…2a6f
2 touches
0 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x1da6be97…9c8d
0x34b655…2a6f
2 touches
0 conflicts
0x26e91541…de96
0x34b655…2a6f
2 touches
0 conflicts
0x3cc4460d…d608
0x34b655…2a6f
2 touches
0 conflicts
0x3ec82b22…1f46
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
0x2941131f86…afcfd2
Audit this contract →
← previous block
·
next block →
recent activity