pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,425,590
← previous block
next block →
recent activity
Analyzing
Block #72,425,590
11 transactions · 7 stateful · 2026-05-04 17:57:46 UTC
Parallelism
82
/100
Blocked
14
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,425,590
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x69f8de91
#3
0x69f8de91
#4
0x69f8de91
#5
0x5bf9264c
#6
0x5bf9264c
#7
0x98717539
#9
updateDataFeedsValuesPartial
#10
setData
#8
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3274ad72…9df8
0x065c9d…c394
4 touches
1 conflict
0x048da630…f686
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x26b38cc7…6974
0x065c9d…c394
3 touches
1 conflict
0xfc297262…8499
0x065c9d…c394
3 touches
1 conflict
0x5c8c6ab6…dc36
0x065c9d…c394
2 touches
0 conflicts
0x9d806682…6057
0x065c9d…c394
2 touches
0 conflicts
0xd044e735…e67e
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
0x3274ad72e2…cf9df8
Audit this contract →
← previous block
·
next block →
recent activity