pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,290,950
← previous block
next block →
recent activity
Analyzing
Block #86,290,950
14 transactions · 13 stateful · 2026-07-07 23:26:51 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,290,950
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
approve
#4
execOrders
· blocks 1
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
cancelLimitOrder
#10
0x6a4d8bb3
#11
cancel
#12
setData
#13
execOrders
#5
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b6e959d…158f
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
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x02df8f7b…9cc1
0x34b655…2a6f
2 touches
0 conflicts
0x0672e4a2…8d1f
0x34b655…2a6f
2 touches
0 conflicts
0x07bb3f5a…617e
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
0x3b6e959d6b…f8158f
Audit this contract →
← previous block
·
next block →
recent activity