pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,959,339
← previous block
next block →
recent activity
Analyzing
Block #85,959,339
13 transactions · 10 stateful · 2026-07-06 10:32:56 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,959,339
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x3f5c179b
#6
0x0f6795d9
#7
0x6a4b84d0
#8
setData
#9
0x2fa7e5…62dc
#10
0x39435dac
#11
0x39435dac
#12
0xc7e3ec2c
#2
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x235390bc…2bf9
0x065c9d…c394
2 touches
0 conflicts
0x2fb90242…a1d1
0x065c9d…c394
2 touches
0 conflicts
0x40e49ccc…b83e
0x065c9d…c394
2 touches
0 conflicts
0x7b9081d8…6147
0x065c9d…c394
2 touches
0 conflicts
0xa4f80979…4d71
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity