pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,035,629
← previous block
next block →
recent activity
Analyzing
Block #73,035,629
14 transactions · 10 stateful · 2026-05-07 13:41:39 UTC
Parallelism
86
/100
Blocked
10
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,035,629
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
exactInputSingle
#6
0x62be7533
#7
updatePosition
#8
0x0c7abd22
#9
createModule
#10
0xeffdedb0
#11
setData
#12
0x39435dac
#13
jMMeC
#2
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd574ca…7ab1
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x37e1be01…6f19
0x54cd53…9e7d
2 touches
0 conflicts
0xa27fa22d…7dca
0x54cd53…9e7d
2 touches
0 conflicts
0x00a18b3c…3ec3
0x6657d1…8ccc
2 touches
0 conflicts
0x046ce0a6…4851
0x6657d1…8ccc
2 touches
0 conflicts
0x06d73738…1335
0x6657d1…8ccc
2 touches
0 conflicts
0x08eb87df…14c2
0x6657d1…8ccc
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:
0xd574cae5…037ab1
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity