pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#82,551,291
← previous block
next block →
recent activity
Analyzing
Block #82,551,291
10 transactions · 8 stateful · 2026-06-20 15:37:04 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,551,291
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#3
0x5a5d9a99
#4
redeemDelegations
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x6a36b418
#8
setData
#9
execOrders
#2
execOrder
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
0x8a7af3fd…72a6
0x34b655…2a6f
4 touches
1 conflict
0xfe2b2202…3ef5
0x34b655…2a6f
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x10fd2c60…b6be
0x188d58…ea8e
2 touches
0 conflicts
0x7fe5a056…b1b7
0x188d58…ea8e
2 touches
0 conflicts
0xeeabeda4…de22
0x188d58…ea8e
2 touches
0 conflicts
0x07bb3f5a…617e
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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
0x8a7af3fdbb…2b72a6
Audit this contract →
← previous block
·
next block →
recent activity