pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,314,675
← previous block
next block →
recent activity
Analyzing
Block #72,314,675
10 transactions · 9 stateful · 2026-05-04 05:38:43 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,314,675
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xed82b078
· blocks 2
#2
0x5bf9264c
#3
0x5bf9264c
#6
collect
#7
updateDataFeedsValuesPartial
#8
0x69f8315a
#9
setData
#4
0x9036287a
· blocks 1
#5
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xcccabc14…cbe4
0x065c9d…c394
4 touches
1 conflict
0xa8eb8704…8036
0x065c9d…c394
3 touches
1 conflict
0x343ba948…2ced
0x065c9d…c394
3 touches
1 conflict
0x35323df1…7129
0x065c9d…c394
2 touches
0 conflicts
0x466589ac…3249
0x065c9d…c394
2 touches
0 conflicts
0xb63fede2…2857
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
3 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity