pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,917,997
← previous block
next block →
recent activity
Analyzing
Block #70,917,997
7 transactions · 6 stateful · 2026-04-27 18:26:48 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,917,997
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
0xb0435a94
· blocks 1
#5
0x69efaae0
#6
setData
#4
0xb0435a94
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b4df54f…7afb
0x754704…b603
4 touches
1 conflict
0xa3dc6f35…13e9
0x754704…b603
4 touches
1 conflict
0x8956cb26…42fa
0x73ada1…8be0
4 touches
1 conflict
0xf4e554ca…1a6c
0x73ada1…8be0
4 touches
1 conflict
0x8376cab2…c72c
0x2e3234…7d90
2 touches
0 conflicts
0x0d622e34…0000
0x681e90…ae09
2 touches
0 conflicts
0x08dabacb…0225
0x73ada1…8be0
2 touches
0 conflicts
0x32562817…845f
0x73ada1…8be0
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:
0x754704bc…afb603
1 conflict on slot
0x1b4df54fde…567afb
Audit this contract →
← previous block
·
next block →
recent activity