pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,181,646
← previous block
next block →
recent activity
Analyzing
Block #85,181,646
12 transactions · 10 stateful · 2026-07-02 20:12:16 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,181,646
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
#3
updatePrices
#4
0x5a5d9a99
· blocks 1
#5
updateDataFeedsValuesPartial
#7
0x6a46c698
#8
setData
#10
0xc7e3ec2c
#11
0xc7e3ec2c
#6
execFwdPositionOps
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x022b49db…a477
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1c04a22d…d43b
0x065c9d…c394
2 touches
0 conflicts
0x44cb7573…df19
0x065c9d…c394
2 touches
0 conflicts
0xbc970459…b7ce
0x065c9d…c394
2 touches
0 conflicts
0xdeed6f69…f136
0x065c9d…c394
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
0xac2a02739b…81721b
Audit this contract →
← previous block
·
next block →
recent activity