pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,296,377
← previous block
next block →
recent activity
Analyzing
Block #72,296,377
9 transactions · 8 stateful · 2026-05-04 03:36:49 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,296,377
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x69f814c9
#2
0x9036287a
· blocks 2
#3
0x98717539
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
setData
#4
0x3f5c179b
· blocks 1
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
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
0xbbee74c2…567a
0x065c9d…c394
4 touches
1 conflict
0x08012a78…50c2
0x065c9d…c394
4 touches
1 conflict
0x24968e6d…0132
0x065c9d…c394
4 touches
1 conflict
0x2e384d50…b649
0x065c9d…c394
3 touches
1 conflict
0x318a17b2…8185
0x065c9d…c394
3 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
2 touches
0 conflicts
0x00000000…000b
0x8d0464…4402
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