pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,394,954
← previous block
next block →
recent activity
Analyzing
Block #72,394,954
6 transactions · 5 stateful · 2026-05-04 14:33:34 UTC
Parallelism
67
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,394,954
· 6 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
setData
#3
0x0c7abd22
· blocks 1
#5
0x69f8aeb6
#4
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7edae8df…d3f5
0x065c9d…c394
4 touches
1 conflict
0x32ca4db5…4402
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x04fa4596…3254
0x065c9d…c394
4 touches
1 conflict
0x78ff739a…881a
0x065c9d…c394
3 touches
1 conflict
0xe26fb919…2119
0x065c9d…c394
3 touches
1 conflict
0x19ed8762…a8b7
0x065c9d…c394
3 touches
1 conflict
0x0e15565e…c0d6
0x065c9d…c394
3 touches
1 conflict
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
0x7edae8dfcd…3bd3f5
Audit this contract →
← previous block
·
next block →
recent activity