pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#70,951,097
← previous block
next block →
recent activity
Analyzing
Block #70,951,097
13 transactions · 11 stateful · 2026-04-27 22:07:06 UTC
Parallelism
85
/100
Blocked
18
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,951,097
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x67098489
· blocks 1
#2
exactOutputSingle
#4
0xb264ae19
#5
0xb3dd4ec4
#6
updatePrices
· blocks 1
#8
0x0c7abd22
#9
updateDataFeedsValuesPartial
#10
0x6463ffd1
#11
0x69efde81
#12
setData
#3
execute
#7
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x00000000…0002
0xb857c1…9be1
4 touches
1 conflict
0x01e7b865…6e6f
0x188d58…ea8e
4 touches
1 conflict
0xe7623543…4dcb
0x188d58…ea8e
2 touches
0 conflicts
0xe7623543…4dcc
0x188d58…ea8e
2 touches
0 conflicts
0x2af5f63a…b7b9
0x2e3234…7d90
2 touches
0 conflicts
0x8956cb26…42f7
0x73ada1…8be0
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:
Uniswap: PoolManager
1 conflict on slot
0x01e7b86585…4d6e6d
Audit this contract →
← previous block
·
next block →
recent activity