pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,877,765
← previous block
next block →
recent activity
Analyzing
Block #70,877,765
8 transactions · 7 stateful · 2026-04-27 13:58:53 UTC
Parallelism
75
/100
Blocked
29
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,877,765
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
0x6463ffd1
· blocks 1
#5
0x69ef6c15
· blocks 1
#6
setData
#4
0x6463ffd1
#7
0x69ef6c15
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x032c41ac…c35a
0x065c9d…c394
4 touches
1 conflict
0x0cce0daa…9d52
0x065c9d…c394
4 touches
1 conflict
0x4c06bb7a…3e1c
0x065c9d…c394
4 touches
1 conflict
0x71c854be…16cb
0x065c9d…c394
4 touches
1 conflict
0xc6d3aa69…082a
0x065c9d…c394
2 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:
0x681e908b…e1ae09
1 conflict on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity