pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,981,957
← previous block
next block →
recent activity
Analyzing
Block #70,981,957
13 transactions · 12 stateful · 2026-04-28 01:32:46 UTC
Parallelism
77
/100
Blocked
17
%
Avg conflicts / tx
0.23
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,981,957
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
dagSwapByOrderId
#2
multicall
#3
updatePrices
#4
0x98717539
#5
updateDataFeedsValuesPartial
#6
approve
#7
0x6463ffd1
· blocks 2
#8
claim
#10
0xed82b078
#11
setData
#9
0xed82b078
· blocks 1
#12
0x23afbff3
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
9
w1
12
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbbee74c2…567a
0x065c9d…c394
6 touches
3 conflicts
0xf7f00987…2695
0x065c9d…c394
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xb1632c2f…d991
0x0a3323…0a3c
2 touches
0 conflicts
0xdeaab6a3…ccad
0x0a3323…0a3c
2 touches
0 conflicts
0x5db918ef…f1ef
0x0c65a0…0852
2 touches
0 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
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
3 conflicts on slot
0xbbee74c2e7…6e567a
Audit this contract →
← previous block
·
next block →
recent activity