pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,995,419
← previous block
next block →
recent activity
Analyzing
Block #70,995,419
7 transactions · 6 stateful · 2026-04-28 03:02:25 UTC
Parallelism
71
/100
Blocked
33
%
Avg conflicts / tx
0.29
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,995,419
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x6463ffd1
· blocks 1
#5
setData
#2
updatePrices
#6
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf009927…c633
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xb857c1…9be1
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x15376a64…f87d
0x065c9d…c394
4 touches
1 conflict
0x28b2b229…15cd
0x065c9d…c394
4 touches
1 conflict
0xf4bdcf41…b8b4
0x065c9d…c394
4 touches
1 conflict
0x9daa1b39…9cd9
0x065c9d…c394
2 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:
0x065c9d28…a9c394
1 conflict on slot
0xbf0099279b…2fc633
Audit this contract →
← previous block
·
next block →
recent activity