pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,218,014
← previous block
next block →
recent activity
Analyzing
Block #74,218,014
9 transactions · 7 stateful · 2026-05-13 01:08:11 UTC
Parallelism
67
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,218,014
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0xcf7468f4
#5
updateDataFeedsValuesPartial
#6
updatePriceFeedsIfNecessary
#7
0x6a03cf72
#8
setData
#2
0x0c7abd22
· blocks 1
#4
0xccf50a51
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf3283ba…c9fa
0x065c9d…c394
4 touches
1 conflict
0x31c342f9…ae5c
0xd32edf…ff58
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x52d75775…9a7f
0x065c9d…c394
2 touches
0 conflicts
0x6aa536f9…a605
0x065c9d…c394
2 touches
0 conflicts
0x9851020c…00c6
0x065c9d…c394
2 touches
0 conflicts
0xf2e6d0ed…d706
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
0xcf3283bab2…c3c9fa
Audit this contract →
← previous block
·
next block →
recent activity