pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,425,864
← previous block
next block →
recent activity
Analyzing
Block #72,425,864
5 transactions · 5 stateful · 2026-05-04 17:59:36 UTC
Parallelism
60
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,425,864
· 5 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x9036287a
· blocks 1
#2
updateDataFeedsValuesPartial
#4
setData
#3
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x291fedf2…e181
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x434306f8…4f77
0x065c9d…c394
3 touches
1 conflict
0x59a5054c…ac40
0x065c9d…c394
3 touches
1 conflict
0x7efb66ba…9876
0x065c9d…c394
2 touches
0 conflicts
0xb949a223…b426
0x065c9d…c394
2 touches
0 conflicts
0xbf643de1…2978
0x065c9d…c394
2 touches
0 conflicts
0xffe431af…8faa
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
0x291fedf2e6…22e181
Audit this contract →
← previous block
·
next block →
recent activity