pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,171,028
← previous block
next block →
recent activity
Analyzing
Block #85,171,028
13 transactions · 11 stateful · 2026-07-02 19:01:28 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,171,028
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
poke
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#6
0x3f5c179b
#7
forward
#8
forward
#9
setData
#11
execOrders
#12
0xc7e3ec2c
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec1d7176…6f5e
0x34b655…2a6f
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01a63428…9f8b
0x34b655…2a6f
2 touches
0 conflicts
0x043488e6…2455
0x34b655…2a6f
2 touches
0 conflicts
0x08d66073…e706
0x34b655…2a6f
2 touches
0 conflicts
0x0f9012d5…10f1
0x34b655…2a6f
2 touches
0 conflicts
0x10816ff2…4cbf
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
0xec1d7176e6…a86f5e
Audit this contract →
← previous block
·
next block →
recent activity