pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,779,469
← previous block
next block →
recent activity
Analyzing
Block #74,779,469
11 transactions · 9 stateful · 2026-05-15 15:35:25 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,779,469
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x575c0012
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
0xc5a04723
#7
0x6a073db5
#8
setData
#9
0x5e1849…0096
#10
0x39435dac
#3
0xcf7468f4
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6af306bb…2e81
0x3bd359…433a
4 touches
1 conflict
0xce8bbe33…b72e
0x3bd359…433a
4 touches
1 conflict
0xbd96f396…e8b6
0x065c9d…c394
4 touches
1 conflict
0x438cf5f6…f077
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xf91b744e…9117
0x754704…b603
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
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:
Wrapped MON (WMON)
1 conflict on slot
0x6af306bb1d…092e81
Audit this contract →
← previous block
·
next block →
recent activity