pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,701,480
← previous block
next block →
recent activity
Analyzing
Block #71,701,480
11 transactions · 10 stateful · 2026-05-01 09:28:11 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,701,480
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
execute
#3
updatePrices
#4
addLiquidity
#5
exec
#6
updateDataFeedsValuesPartial
#7
0xeffdedb0
#8
withdraw
#10
setData
#9
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f8eb721…2f79
0x065c9d…c394
4 touches
1 conflict
0xec7080f5…2538
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xef7e7937…95c7
0x065c9d…c394
3 touches
1 conflict
0x148b71d7…5ca2
0x065c9d…c394
3 touches
1 conflict
0x71cce570…5dea
0x065c9d…c394
3 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
2 touches
0 conflicts
0x6e5da90a…3cb6
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
0x4f8eb7211e…4d2f79
Audit this contract →
← previous block
·
next block →
recent activity