pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,995,859
← previous block
next block →
recent activity
Analyzing
Block #70,995,859
9 transactions · 8 stateful · 2026-04-28 03:05:21 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,995,859
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
multicall
#2
updateDataFeedsValuesPartial
#3
setData
#4
0xa09e9040
#5
updatePrices
#6
updatePrices
· blocks 2
#7
updatePrices
· blocks 1
#8
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0xc1a578…8e1a
6 touches
3 conflicts
0x00000000…0000
0xc1a578…8e1a
6 touches
3 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1c601885…a733
0x065c9d…c394
2 touches
0 conflicts
0x252830dd…2b86
0x065c9d…c394
2 touches
0 conflicts
0x2578f3dc…b3d7
0x2a68ba…90c5
2 touches
0 conflicts
0x2af5f63a…b7b9
0x2e3234…7d90
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:
0xc1a5781e…c78e1a
3 conflicts on slot
0x0000000000…000001
Audit this contract →
← previous block
·
next block →
recent activity