pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,350,880
← previous block
next block →
recent activity
Analyzing
Block #85,350,880
13 transactions · 11 stateful · 2026-07-03 14:59:30 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
#85,350,880
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updatePrices
· blocks 1
#4
borrow
#5
0x5a5d9a99
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
0xed82b078
#10
setData
#11
0xbb9258…1a75
#12
execOrders
#3
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
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
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x08e8f2c9…a11a
0x34b655…2a6f
2 touches
0 conflicts
0x2bf5914f…c75d
0x34b655…2a6f
2 touches
0 conflicts
0xfefb0189…f726
0x34b655…2a6f
2 touches
0 conflicts
0x1f4f98fc…6c48
0x57ea24…2cec
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