pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,752,247
← previous block
next block →
recent activity
Analyzing
Block #85,752,247
10 transactions · 9 stateful · 2026-07-05 11:33:23 UTC
Parallelism
60
/100
Blocked
33
%
Avg conflicts / tx
0.6
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,752,247
· 10 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
executePacked
#2
updateDataFeedsValuesPartial
#3
updatePrices
· blocks 3
#7
execFwdPositionOps
#8
0x3f5c179b
#9
setData
#4
updatePrices
· blocks 2
#5
updatePrices
· blocks 1
#6
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
6
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x9fc8b97d…96da
0x2a68ba…90c5
2 touches
0 conflicts
0x09500602…94e9
0x34b655…2a6f
2 touches
0 conflicts
0xdf1a8807…22e2
0x40c49f…2af0
2 touches
0 conflicts
0x58a864a6…57e3
0x754704…b603
2 touches
0 conflicts
0x74fa2096…56ea
0x754704…b603
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:
0x04fdeac2…f747d7
6 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity