pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,289,425
← previous block
next block →
recent activity
Analyzing
Block #71,289,425
9 transactions · 8 stateful · 2026-04-29 11:39:35 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,289,425
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x20601463
· blocks 1
#4
0x39435dac
#5
0x69f1ee6e
#6
setData
#7
updatePrices
#8
updatePrices
#3
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x13700c71…896a
0x065c9d…c394
2 touches
0 conflicts
0x8f313589…99bf
0x065c9d…c394
2 touches
0 conflicts
0x964f809c…1c46
0x065c9d…c394
2 touches
0 conflicts
0xa87480dd…905b
0x065c9d…c394
2 touches
0 conflicts
0xd51bedbb…2b2c
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity