pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#72,284,129
← previous block
next block →
recent activity
Analyzing
Block #72,284,129
25 transactions · 15 stateful · 2026-05-04 02:14:34 UTC
Parallelism
80
/100
Blocked
27
%
Avg conflicts / tx
0.4
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,284,129
· 25 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
0x69f80181
· blocks 4
#6
0x69f80180
#7
0x69f80181
#8
0x69f80181
#9
0x69f80181
#10
0x69f80181
#11
addLiquidity
#12
updateDataFeedsValuesPartial
#13
updateDataFeedsValuesPartial
#14
updateDataFeedsValuesPartial
#15
updateDataFeedsValuesPartial
#16
0x69f80181
#17
0x3f5c179b
#18
forward
#19
0x6df9e92b
#20
0x39435dac
#21
modifyLiquidities
#22
0x69f80181
#23
setData
#24
0x39435dac
#2
0x69f80181
· blocks 3
#3
0x69f80181
· blocks 2
#4
0x69f80181
· blocks 1
#5
0x69f80182
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
5
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
10 touches
10 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1887679d…5fb7
0x065c9d…c394
2 touches
0 conflicts
0x24968e6d…0132
0x065c9d…c394
2 touches
0 conflicts
0xbad103ed…91ce
0x065c9d…c394
2 touches
0 conflicts
0xef675236…ca32
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:
0x681e908b…e1ae09
10 conflicts on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity