pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,314,867
← previous block
next block →
recent activity
Analyzing
Block #72,314,867
8 transactions · 7 stateful · 2026-05-04 05:39:59 UTC
Parallelism
75
/100
Blocked
29
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,314,867
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98717539
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0x69f831a7
· blocks 1
#5
setData
#7
0x39435dac
#4
0x69f831a7
#6
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9d2cf20…a668
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x005fb969…2d97
0x34b655…2a6f
2 touches
0 conflicts
0x17e2d2a0…359e
0x34b655…2a6f
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x2877f440…c2c8
0x34b655…2a6f
2 touches
0 conflicts
0x2a00efe7…6ff2
0x34b655…2a6f
2 touches
0 conflicts
0x2fb27064…b8c2
0x34b655…2a6f
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:
0x34b6552d…112a6f
1 conflict on slot
0xb9d2cf2005…28a668
Audit this contract →
← previous block
·
next block →
recent activity