pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,489,524
← previous block
next block →
recent activity
Analyzing
Block #86,489,524
13 transactions · 11 stateful · 2026-07-08 21:33:53 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,489,524
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
0x5a5d9a99
#4
0x5a5d9a99
#5
0x5a5d9a99
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
batchUpdatePrice
#9
setData
#10
0x4e4670…7dcf
#11
execOrders
· blocks 1
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8765edd1…a7d5
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x28504822…ded6
0x34b655…2a6f
2 touches
0 conflicts
0x4caf91f9…8ab5
0x34b655…2a6f
2 touches
0 conflicts
0x548145a9…cfce
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
0x8765edd17a…a5a7d5
Audit this contract →
← previous block
·
next block →
recent activity