pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,762,014
← previous block
next block →
recent activity
Analyzing
Block #85,762,014
10 transactions · 9 stateful · 2026-07-05 12:38:17 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,762,014
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#6
0x6df9e92b
#7
setData
#8
execOrders
#9
0xc7e3ec2c
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ee7744e…8ddc
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x489cb750…7069
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xb4dedd16…9804
0x065c9d…c394
3 touches
1 conflict
0x2d255707…c3ab
0x065c9d…c394
2 touches
0 conflicts
0x3d1fca16…d653
0x065c9d…c394
2 touches
0 conflicts
0xc4f20b73…6e73
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x1ee7744eaf…dd8ddc
Audit this contract →
← previous block
·
next block →
recent activity