pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,425,737
← previous block
next block →
recent activity
Analyzing
Block #72,425,737
6 transactions · 6 stateful · 2026-05-04 17:58:45 UTC
Parallelism
67
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,425,737
· 6 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69f8decc
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
#5
setData
#2
0x69f8decc
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x28f5418f…cb14
0x065c9d…c394
2 touches
0 conflicts
0x6a77520d…bf29
0x065c9d…c394
2 touches
0 conflicts
0x810a6487…4fa3
0x065c9d…c394
2 touches
0 conflicts
0xb8b05c3b…077c
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:
0x681e908b…e1ae09
1 conflict on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity