pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,504,450
← previous block
next block →
recent activity
Analyzing
Block #86,504,450
13 transactions · 11 stateful · 2026-07-08 23:13:26 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,504,450
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
0x98717539
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
#7
0x6df9e92b
#9
0x6a4eda0e
#10
setData
#11
0x2345a0…3828
#12
execOrders
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7013be2…c0a8
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
0x09500602…94e9
0x34b655…2a6f
2 touches
0 conflicts
0x09500602…94ea
0x34b655…2a6f
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x1cda18d5…31c3
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
0xa7013be2a1…9ac0a8
Audit this contract →
← previous block
·
next block →
recent activity