pev
.
One block, wave by wave
→
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#81,630,255
← previous block
next block →
recent activity
Analyzing
Block #81,630,255
15 transactions · 12 stateful · 2026-06-16 09:14:01 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#81,630,255
· 15 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
supply
#2
0xed82b078
· blocks 2
#4
0xed82b078
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
redeemDelegations
#8
updatePrices
· blocks 1
#10
updatePrices
#11
collect
#12
setData
#13
0x785f5745
#3
0xab083028
· blocks 1
#9
updatePrices
#14
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
8
w0
9
w1
14
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52e69143…95ad
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0002
0xaa7ee7…f0e4
4 touches
1 conflict
0x4035d387…e5bc
0x065c9d…c394
3 touches
1 conflict
0xce827910…ff22
0x065c9d…c394
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x0336241d…4001
0x386489…7508
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
3 conflicts on slot
0x52e6914362…6e95ad
Audit this contract →
← previous block
·
next block →
recent activity