pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,291,497
← previous block
next block →
recent activity
Analyzing
Block #76,291,497
12 transactions · 10 stateful · 2026-05-22 15:51:30 UTC
Parallelism
75
/100
Blocked
30
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,291,497
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x5339c59f
· blocks 2
#3
updatePrices
· blocks 1
#5
updatePrices
#8
redeemDelegations
#9
0x0f6795d9
#10
0x0f6795d9
#11
setData
#4
updatePrices
#6
0xab083028
· blocks 1
#7
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x348fda08…7e96
0x065c9d…c394
6 touches
3 conflicts
0x1fff6dcb…b3f4
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x8488f10f…9354
0x1d1325…2305
4 touches
1 conflict
0x8488f10f…9355
0x1d1325…2305
4 touches
1 conflict
0x8488f10f…9356
0x1d1325…2305
4 touches
1 conflict
0xa605468c…1bfc
0x1d1325…2305
4 touches
1 conflict
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
0x348fda08cf…fc7e96
Audit this contract →
← previous block
·
next block →
recent activity