pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,911,376
← previous block
next block →
recent activity
Analyzing
Block #70,911,376
8 transactions · 7 stateful · 2026-04-27 17:42:40 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,911,376
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x6463ffd1
#3
updatePriceFeedsIfNecessary
#4
0xb0435a94
· blocks 1
#6
0x69efa088
#7
setData
#5
0xb0435a94
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
0xf4e554ca…1a6c
0x73ada1…8be0
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2688f1ff…3530
0x065c9d…c394
2 touches
0 conflicts
0x283016e3…29c4
0x065c9d…c394
2 touches
0 conflicts
0x47d32340…e9e9
0x065c9d…c394
2 touches
0 conflicts
0xaeb910a9…3a44
0x065c9d…c394
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:
0x73ada1ea…808be0
1 conflict on slot
0xf4e554ca04…9c1a6c
Audit this contract →
← previous block
·
next block →
recent activity