pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,908,659
← previous block
next block →
recent activity
Analyzing
Block #70,908,659
9 transactions · 6 stateful · 2026-04-27 17:24:34 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,908,659
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
updatePrices
#4
0x5bf9264c
#5
0x5bf9264c
#6
0x6463ffd1
#7
updateDataFeedsValuesPartial
#8
setData
#2
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb857c1…9be1
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0cafcd74…adc5
0x065c9d…c394
2 touches
0 conflicts
0x1e2bddaa…8ec0
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:
0xb857c13a…1a9be1
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity