pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,986,728
← previous block
next block →
recent activity
Analyzing
Block #70,986,728
8 transactions · 7 stateful · 2026-04-28 02:04:31 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,986,728
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
setData
#5
0x6463ffd1
· blocks 1
#7
0x69f01627
#6
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0f49abc5…b8a1
0x065c9d…c394
4 touches
1 conflict
0x6e0dc6a1…2922
0x065c9d…c394
4 touches
1 conflict
0xaf40174d…0b3b
0x065c9d…c394
4 touches
1 conflict
0xb1cddb0e…1215
0x065c9d…c394
4 touches
1 conflict
0xbea59939…b035
0x065c9d…c394
4 touches
1 conflict
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
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