pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,314,930
← previous block
next block →
recent activity
Analyzing
Block #72,314,930
9 transactions · 8 stateful · 2026-05-04 05:40:24 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,314,930
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x9036287a
· blocks 2
#2
exactOutputSingle
#4
removeLiquidity
#5
updateDataFeedsValuesPartial
#7
setData
#8
0x39435dac
#3
0xb264ae19
· blocks 1
#6
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf823e97f…2ee6
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2efd4a86…3aa3
0x065c9d…c394
3 touches
1 conflict
0x9c00c985…0dc6
0x065c9d…c394
3 touches
1 conflict
0x74e71984…ae90
0x2a68ba…90c5
2 touches
0 conflicts
0x807e1273…3c99
0x3bd359…433a
2 touches
0 conflicts
0xcce2fd99…a8eb
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x659bd0…a9da
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:
0x065c9d28…a9c394
3 conflicts on slot
0xf823e97fa0…262ee6
Audit this contract →
← previous block
·
next block →
recent activity