pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,167,306
← previous block
next block →
recent activity
Analyzing
Block #72,167,306
11 transactions · 9 stateful · 2026-05-03 13:09:33 UTC
Parallelism
64
/100
Blocked
33
%
Avg conflicts / tx
0.55
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,167,306
· 11 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
updatePrices
· blocks 3
#2
updatePrices
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x785f5745
#10
0x3f5c179b
#3
updatePrices
· blocks 2
#4
updatePrices
· blocks 1
#5
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
5
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x7e9d3a…9fda
8 touches
6 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
0x490911cc…5fea
0x0c65a0…0852
2 touches
0 conflicts
0x76728454…6659
0x0c65a0…0852
2 touches
0 conflicts
0x5860c4f3…0c39
0x3bd359…433a
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
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:
0x7e9d3a8a…4f9fda
6 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity