pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,877,739
← previous block
next block →
recent activity
Analyzing
Block #70,877,739
12 transactions · 12 stateful · 2026-04-27 13:58:43 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,877,739
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
updatePrices
#3
0x98717539
· blocks 1
#4
0x6463ffd1
#5
updateDataFeedsValuesPartial
#6
0x0c7abd22
#7
setData
#9
updatePrices
· blocks 1
#11
updatePrices
#8
0x39435dac
#10
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41335ddf…94b9
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0000
0xc1a578…8e1a
4 touches
1 conflict
0x00000000…0001
0xc1a578…8e1a
4 touches
1 conflict
0x4d017ee7…3542
0x73ada1…8be0
2 touches
0 conflicts
0x6abb9910…d1ea
0x73ada1…8be0
2 touches
0 conflicts
0x6f2f0e48…5f17
0x73ada1…8be0
2 touches
0 conflicts
0x8956cb26…42f7
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:
0x34b6552d…112a6f
1 conflict on slot
0x41335ddf94…5594b9
Audit this contract →
← previous block
·
next block →
recent activity