pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,133,799
← previous block
next block →
recent activity
Analyzing
Block #86,133,799
12 transactions · 10 stateful · 2026-07-07 05:57:43 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,133,799
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
execOrders
#4
execOrders
· blocks 1
#5
execOrders
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
execOrders
#10
setData
#11
execOrders
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0d3a786…91d9
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x2b648bb8…aade
0x34b655…2a6f
2 touches
0 conflicts
0x53b4ef2b…8a05
0x34b655…2a6f
2 touches
0 conflicts
0x59dbc306…f976
0x34b655…2a6f
2 touches
0 conflicts
0x608ebd53…deda
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
0xa0d3a786de…b991d9
Audit this contract →
← previous block
·
next block →
recent activity