pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,074,814
← previous block
next block →
recent activity
Analyzing
Block #86,074,814
10 transactions · 9 stateful · 2026-07-06 23:24:07 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,074,814
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
execOrders
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
swap
#8
execFwdPositionOps
#9
setData
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9e23360…8ef7
0x34b655…2a6f
4 touches
1 conflict
0x2c5edd82…074a
0x34b655…2a6f
4 touches
1 conflict
0x4d4389b2…6e07
0x34b655…2a6f
2 touches
0 conflicts
0x608ebd53…deda
0x34b655…2a6f
2 touches
0 conflicts
0x86cea35b…bdff
0x34b655…2a6f
2 touches
0 conflicts
0xaea2f389…0305
0x34b655…2a6f
2 touches
0 conflicts
0xec0e0220…cb90
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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
0xf9e23360ff…e88ef7
Audit this contract →
← previous block
·
next block →
recent activity