pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,394,981
← previous block
next block →
recent activity
Analyzing
Block #72,394,981
8 transactions · 8 stateful · 2026-05-04 14:33:45 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,394,981
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
redeemDelegations
#3
0x0c7abd22
· blocks 1
#5
forward
#6
0x39435dac
#7
setData
#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
0x48c6e5aa…cc95
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x45eab05c…7cfb
0x065c9d…c394
3 touches
1 conflict
0xab876489…d84c
0x065c9d…c394
3 touches
1 conflict
0x85946e90…7fd6
0x0c65a0…0852
2 touches
0 conflicts
0xaf41644f…8f2e
0x0c65a0…0852
2 touches
0 conflicts
0x373f94db…c177
0x3bd359…433a
2 touches
0 conflicts
0x3de215fe…c018
0x3bd359…433a
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
0x48c6e5aa20…21cc95
Audit this contract →
← previous block
·
next block →
recent activity