pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,283,169
← previous block
next block →
recent activity
Analyzing
Block #72,283,169
12 transactions · 10 stateful · 2026-05-04 02:08:06 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,283,169
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
#2
0x40e79b1b
· blocks 1
#3
0x5bf9264c
#4
0x5bf9264c
#5
0x69f7fffd
· blocks 1
#7
0x98717539
#8
updateDataFeedsValuesPartial
#10
0x9e76c652
#11
setData
#6
0x69f7fffd
#9
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w0
6
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xdf0cfbe3…4007
0x065c9d…c394
2 touches
0 conflicts
0x8d3ae14e…1753
0x2a68ba…90c5
2 touches
0 conflicts
0x005fb969…2d97
0x34b655…2a6f
2 touches
0 conflicts
0x1279ee2d…ae99
0x34b655…2a6f
2 touches
0 conflicts
0x157d1e46…85f6
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:
0x065c9d28…a9c394
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity