pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,862,938
← previous block
next block →
recent activity
Analyzing
Block #70,862,938
15 transactions · 14 stateful · 2026-04-27 12:20:07 UTC
Parallelism
87
/100
Blocked
21
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,862,938
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xe0de3ed7
#2
0x42dd8743
#3
execute
· blocks 1
#5
updatePrices
#6
0x0c7abd22
· blocks 1
#7
0x96e62922
#8
updateDataFeedsValuesPartial
#9
setData
#10
updatePrices
· blocks 1
#11
updatePrices
#14
0x5d2fd812
#4
execute
#12
updatePrices
#13
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w0
10
w0
12
w1
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0xc1a578…8e1a
4 touches
1 conflict
0x00000000…0001
0xc1a578…8e1a
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
4 touches
1 conflict
0x83bb206d…7d45
0xd32edf…ff58
3 touches
1 conflict
0x78ae17f2…53be
0x000000…012a
2 touches
0 conflicts
0x00000000…0001
0x010592…1c83
2 touches
0 conflicts
0x00000000…0006
0x010592…1c83
2 touches
0 conflicts
0x072274c8…950c
0x010592…1c83
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:
0xc1a5781e…c78e1a
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity