pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,917,647
← previous block
next block →
recent activity
Analyzing
Block #70,917,647
9 transactions · 7 stateful · 2026-04-27 18:24:28 UTC
Parallelism
67
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,917,647
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xc5a04723
#2
0xed82b078
· blocks 1
#5
updateDataFeedsValuesPartial
#6
setData
#7
updatePrices
#8
updatePrices
#3
0xed82b078
· blocks 1
#4
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x24968e6d…0132
0x065c9d…c394
2 touches
0 conflicts
0xb94e8a5f…43e8
0x065c9d…c394
2 touches
0 conflicts
0xf62ca3b6…7abe
0x065c9d…c394
2 touches
0 conflicts
0xc6f1b3af…c97c
0x1001ff…1001
2 touches
0 conflicts
0xe5b1eb58…7644
0x1001ff…1001
2 touches
0 conflicts
0x00000000…003d
0x131a2e…0da9
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity