pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,631,489
← previous block
next block →
recent activity
Analyzing
Block #86,631,489
14 transactions · 10 stateful · 2026-07-09 13:24:04 UTC
Parallelism
86
/100
Blocked
10
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,631,489
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
withdraw
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
executeBatch
#9
batchUpdate
#10
setData
#11
0xff12ab…35df
#12
0xa8f4cb…a829
#13
0xb8024e7f
#2
updatePrices
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
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1800b40c…bc23
0x34b655…2a6f
2 touches
0 conflicts
0x349cfcd7…b6a8
0x34b655…2a6f
2 touches
0 conflicts
0x349cfcd7…b6a9
0x34b655…2a6f
2 touches
0 conflicts
0x44aa74de…9b58
0x34b655…2a6f
2 touches
0 conflicts
0x469dac8d…3411
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:
0x04fdeac2…f747d7
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity