pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,962,948
← previous block
next block →
recent activity
Analyzing
Block #73,962,948
14 transactions · 11 stateful · 2026-05-11 20:48:37 UTC
Parallelism
86
/100
Blocked
9
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,962,948
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execute
#3
addLiquidity
#4
collect
#5
updateFeeds
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x6a02411d
#9
setData
#10
0x2cd48c…feec
#11
0x57014d…a952
#12
0x39435dac
· blocks 1
#13
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
12
w0
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd79c9727…1233
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2667680c…43f8
0x065c9d…c394
2 touches
0 conflicts
0x3c12b65a…a60e
0x065c9d…c394
2 touches
0 conflicts
0x6d8ac73a…b1f6
0x065c9d…c394
2 touches
0 conflicts
0xf0ae7683…6d50
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:
Perpl
1 conflict on slot
0xd79c972734…f71233
Audit this contract →
← previous block
·
next block →
recent activity