pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,846,267
← previous block
next block →
recent activity
Analyzing
Block #70,846,267
9 transactions · 9 stateful · 2026-04-27 10:29:02 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,846,267
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
updateDataFeedsValuesPartial
#3
spin
#4
0x6463ffd1
· blocks 1
#6
0x69ef3ae6
#7
setData
#8
updatePrices
#5
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b15ccae…c3c2
0x065c9d…c394
4 touches
1 conflict
0xa78781f8…6e77
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x235eb5e3…53b2
0x065c9d…c394
4 touches
1 conflict
0x3aeb73d1…2967
0x065c9d…c394
4 touches
1 conflict
0x7833e14c…35ef
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x8956cb26…42fd
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:
0x065c9d28…a9c394
1 conflict on slot
0x9b15ccae92…ddc3c2
Audit this contract →
← previous block
·
next block →
recent activity