pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#77,508,930
← previous block
next block →
recent activity
Analyzing
Block #77,508,930
16 transactions · 15 stateful · 2026-05-28 07:01:44 UTC
Parallelism
88
/100
Blocked
7
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#77,508,930
· 16 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
exactInputSingle
#3
setPrice
#4
setPrice
#5
setPrice
#6
setPrice
#7
setPrice
#8
setPrice
#9
setPrice
#10
0xab083028
· blocks 1
#11
updateDataFeedsValuesPartial
#13
0x29eed2d3
#14
commit
#15
setData
#12
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0xbc1b8309…15d9
0x065c9d…c394
4 touches
1 conflict
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x136a2948…318b
0x065c9d…c394
3 touches
1 conflict
0x6d6363bf…ab76
0x065c9d…c394
3 touches
1 conflict
0x7b43f938…3650
0x000000…012a
2 touches
0 conflicts
0x4dd1db39…a994
0x188d58…ea8e
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
0x52e6914362…6e95ad
Audit this contract →
← previous block
·
next block →
recent activity