pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,352,940
← previous block
next block →
recent activity
Analyzing
Block #85,352,940
13 transactions · 12 stateful · 2026-07-03 15:13:14 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,352,940
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0xab083028
#3
updatePrices
#4
updatePrices
#5
0x39435dac
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
executeBatch
#10
0x0f6795d9
#11
setData
#12
0xc7e3ec2c
#9
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
9
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
0x479503d1…2799
0x065c9d…c394
2 touches
0 conflicts
0x5ac34787…9b4e
0x065c9d…c394
2 touches
0 conflicts
0x89721131…28ac
0x065c9d…c394
2 touches
0 conflicts
0x8b043f30…277f
0x065c9d…c394
2 touches
0 conflicts
0x99029136…0eb7
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