pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,922,697
← previous block
next block →
recent activity
Analyzing
Block #70,922,697
11 transactions · 11 stateful · 2026-04-27 18:58:04 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,922,697
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x98717539
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x6463ffd1
· blocks 1
#6
relay
#7
forward
#8
0x69efb234
#9
setData
#5
0x6463ffd1
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w0
5
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb1747e2…f78b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe2e8270d…7d70
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x19f32839…8a71
0x065c9d…c394
3 touches
1 conflict
0xbc8d26b8…b6ca
0x065c9d…c394
3 touches
1 conflict
0xf46db129…8ff4
0x065c9d…c394
3 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
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:
0x34b6552d…112a6f
1 conflict on slot
0xbb1747e217…82f78b
Audit this contract →
← previous block
·
next block →
recent activity