pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#81,879,530
← previous block
next block →
recent activity
Analyzing
Block #81,879,530
9 transactions · 7 stateful · 2026-06-17 12:54:58 UTC
Parallelism
67
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#81,879,530
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute_route
#2
updateDataFeedsValuesPartial
#3
execOrders
· blocks 1
#4
setData
#5
redeemDelegations
#7
execFwdPositionOps
#6
execFwdPositionOps
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd92b5477…ca84
0x34b655…2a6f
4 touches
1 conflict
0x76409f96…0ca6
0x34b655…2a6f
4 touches
1 conflict
0x9aff966c…53ce
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x1175233a…64e7
0x34b655…2a6f
2 touches
0 conflicts
0x4696bc48…e21a
0x34b655…2a6f
2 touches
0 conflicts
0x54a035dd…16c6
0x34b655…2a6f
2 touches
0 conflicts
0x7f1513ef…55e8
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
0xd92b5477d5…2fca84
Audit this contract →
← previous block
·
next block →
recent activity