pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,575,759
← previous block
next block →
recent activity
Analyzing
Block #72,575,759
11 transactions · 10 stateful · 2026-05-05 10:37:42 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,575,759
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
· blocks 1
#2
updatePrices
#3
0x5bf9264c
#4
0x5bf9264c
#6
forward
#7
updateDataFeedsValuesPartial
#8
0x69f9c8ed
#9
setData
#10
0x39435dac
#5
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x499310eb…6731
0x065c9d…c394
2 touches
0 conflicts
0x80e50d19…6ebb
0x065c9d…c394
2 touches
0 conflicts
0x97048fd7…cde1
0x065c9d…c394
2 touches
0 conflicts
0xb48e993c…0fd2
0x065c9d…c394
2 touches
0 conflicts
0xbbee74c2…567a
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