pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,922,497
← previous block
next block →
recent activity
Analyzing
Block #85,922,497
9 transactions · 7 stateful · 2026-07-06 06:27:15 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,922,497
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
updatePriceFeedsIfNecessary
#3
execFwdPositionOps
· blocks 1
#4
0xed82b078
#6
updateDataFeedsValuesPartial
#7
setData
#8
0xb8e3ce…9539
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d3dac50…4731
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd0307951…f0ea
0x34b655…2a6f
4 touches
1 conflict
0x03622417…0bd6
0x2880ab…7b43
2 touches
0 conflicts
0x03622417…0bd7
0x2880ab…7b43
2 touches
0 conflicts
0x05e5ce66…b69d
0x2880ab…7b43
2 touches
0 conflicts
0x05e5ce66…b69e
0x2880ab…7b43
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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
0x1d3dac5001…284731
Audit this contract →
← previous block
·
next block →
recent activity