pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,130,171
← previous block
next block →
recent activity
Analyzing
Block #85,130,171
11 transactions · 10 stateful · 2026-07-02 14:29:18 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,130,171
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 2
#2
updateDataFeedsValuesPartial
#3
0x3f5c179b
#4
0x3f5c179b
#5
0xf5d05576
#6
0x6a467636
#7
setData
#10
0xc7e3ec2c
#8
execOrders
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebc52107…becf
0x34b655…2a6f
4 touches
1 conflict
0x5b353877…605d
0x34b655…2a6f
4 touches
1 conflict
0x6437175c…b53c
0x34b655…2a6f
4 touches
1 conflict
0x68c07cb9…ae14
0x34b655…2a6f
4 touches
1 conflict
0x7fffd49d…772a
0x34b655…2a6f
4 touches
1 conflict
0x93d03524…0992
0x34b655…2a6f
4 touches
1 conflict
0x9fd37234…2731
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
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
0xebc52107bc…5bbecf
Audit this contract →
← previous block
·
next block →
recent activity