pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#72,575,285
← previous block
next block →
recent activity
Analyzing
Block #72,575,285
10 transactions · 7 stateful · 2026-05-05 10:34:33 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,575,285
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x69f9c830
#3
0x9036287a
· blocks 1
#4
0x893997…68d5
#6
forward
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x0bb13e…016b
#5
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97048fd7…cde1
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4660fa65…e5c0
0x065c9d…c394
3 touches
1 conflict
0x5189d94c…ed10
0x065c9d…c394
3 touches
1 conflict
0x626710e1…c520
0x065c9d…c394
2 touches
0 conflicts
0x78232223…9f5f
0x065c9d…c394
2 touches
0 conflicts
0xe88f8c89…4c9b
0x065c9d…c394
2 touches
0 conflicts
0xf659ca85…2716
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
0x97048fd74c…27cde1
Audit this contract →
← previous block
·
next block →
recent activity