pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,908,597
← previous block
next block →
recent activity
Analyzing
Block #70,908,597
16 transactions · 12 stateful · 2026-04-27 17:24:10 UTC
Parallelism
88
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,908,597
· 16 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
multicall
#3
updatePrices
· blocks 1
#4
updatePrices
#6
updatePrices
#7
updatePrices
#8
updatePrices
#9
updateDataFeedsValuesPartial
#10
updateDataFeedsValuesPartial
#11
0x6463ffd1
· blocks 1
#13
setData
#14
updatePrices
#15
updatePrices
#5
updatePrices
#12
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb857c1…9be1
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1b677063…2d4a
0x065c9d…c394
4 touches
1 conflict
0x2b2ed7c6…113b
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x092527cc…66b9
0x065c9d…c394
3 touches
1 conflict
0xd4ec1e78…b6ff
0x065c9d…c394
3 touches
1 conflict
0xff7f5010…ae3c
0x065c9d…c394
3 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:
0xb857c13a…1a9be1
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity