pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#80,102,141
← previous block
next block →
recent activity
Analyzing
Block #80,102,141
11 transactions · 8 stateful · 2026-06-09 07:29:55 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,102,141
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execPerpOps
#4
execPerpOps
#5
0x98717539
· blocks 1
#7
exactInputSingle
#8
0x6a27c16b
#9
setData
#10
0x0b51f5…0ff8
#6
0x98717539
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
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x015bcfcb…c10c
0x34b655…2a6f
2 touches
0 conflicts
0x08cee64c…a9c4
0x34b655…2a6f
2 touches
0 conflicts
0x08e8f2c9…a11a
0x34b655…2a6f
2 touches
0 conflicts
0x17904ee2…3148
0x34b655…2a6f
2 touches
0 conflicts
0x1e42621c…605b
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
0x90f07a4ff9…b3d932
Audit this contract →
← previous block
·
next block →
recent activity