pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,911,552
← previous block
next block →
recent activity
Analyzing
Block #70,911,552
13 transactions · 11 stateful · 2026-04-27 17:43:51 UTC
Parallelism
69
/100
Blocked
36
%
Avg conflicts / tx
0.38
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,911,552
· 13 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0xe0de3ed7
#2
0xccf50a51
· blocks 3
#4
updatePrices
#5
forward
#6
updateDataFeedsValuesPartial
#7
setData
#10
forward
#11
0x39435dac
#3
0x42dd8743
· blocks 1
#9
swap
#8
0x0c7abd22
· blocks 1
#12
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
8
w2
9
w1
12
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe818ea46…7d6b
0x065c9d…c394
6 touches
3 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xc9b2f016…61a4
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0000
0x059114…ac3b
2 touches
0 conflicts
0x00000000…0001
0x059114…ac3b
2 touches
0 conflicts
0x00000000…0002
0x059114…ac3b
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:
0x065c9d28…a9c394
3 conflicts on slot
0xe818ea4604…0b7d6b
Audit this contract →
← previous block
·
next block →
recent activity