pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,542,541
← previous block
next block →
recent activity
Analyzing
Block #85,542,541
14 transactions · 13 stateful · 2026-07-04 12:15:41 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
#85,542,541
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xab083028
#3
updateDataFeedsValuesPartial
#4
updatePrices
#5
execFwdPositionOps
#6
execFwdPositionOps
· blocks 1
#7
execOrders
#9
updateDataFeedsValuesPartial
#10
0x445e1eb7
#11
setData
#12
execOrders
#13
0xc7e3ec2c
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30faf03c…78b1
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0019
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0029
0x1b6862…e19c
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
0x30faf03c2d…0178b1
Audit this contract →
← previous block
·
next block →
recent activity