pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,360,467
← previous block
next block →
recent activity
Analyzing
Block #73,360,467
13 transactions · 11 stateful · 2026-05-09 01:42:47 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,360,467
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0xa96df62f
#3
0x5bf9264c
#4
0x5bf9264c
#5
updateDataFeedsValuesPartial
#6
forward
#7
0x5339c59f
· blocks 1
#9
0x5339c59f
#10
0x69fe918e
#11
0xeffdedb0
#12
setData
#8
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x02af046e…e34a
0x065c9d…c394
2 touches
0 conflicts
0x1de6403d…5bf6
0x065c9d…c394
2 touches
0 conflicts
0x79ba9346…6152
0x065c9d…c394
2 touches
0 conflicts
0x8f5f4694…b6f3
0x065c9d…c394
2 touches
0 conflicts
0xa5c22cce…7e46
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:
0x065c9d28…a9c394
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity