pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,560,162
← previous block
next block →
recent activity
Analyzing
Block #84,560,162
10 transactions · 10 stateful · 2026-06-29 23:07:21 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,560,162
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
executeBatch
#6
0xed82b078
#7
0x6a42fb21
#8
setData
#9
execOrders
#2
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x21a2a42f…5b43
0x34b655…2a6f
2 touches
0 conflicts
0x27a5ac8c…fd5a
0x34b655…2a6f
2 touches
0 conflicts
0x3c78ca04…432c
0x34b655…2a6f
2 touches
0 conflicts
0x55219c1f…adb6
0x34b655…2a6f
2 touches
0 conflicts
0x5922589d…474d
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
0x6f132c01d5…7dcdcd
Audit this contract →
← previous block
·
next block →
recent activity