pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,956,899
← previous block
next block →
recent activity
Analyzing
Block #70,956,899
10 transactions · 10 stateful · 2026-04-27 22:45:44 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,956,899
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0d484c28
#2
updatePrices
#3
0x98717539
#4
0x6463ffd1
· blocks 2
#6
0xed82b078
· blocks 1
#8
updateDataFeedsValuesPartial
#9
setData
#5
0x6463ffd1
· blocks 1
#7
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w0
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x205ac548…7320
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x04a676d6…6314
0x065c9d…c394
4 touches
1 conflict
0x39662e90…e0f6
0x065c9d…c394
4 touches
1 conflict
0xf7d1adbe…280d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x2c3ab5eb…e68a
0x065c9d…c394
3 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
3 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity