pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,878,019
← previous block
next block →
recent activity
Analyzing
Block #70,878,019
16 transactions · 7 stateful · 2026-04-27 14:00:35 UTC
Parallelism
88
/100
Blocked
14
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,878,019
· 16 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69ef6c7b
#2
updatePrices
#3
updatePrices
#4
updatePrices
#5
updatePrices
#6
updatePrices
#7
postPrice
#8
0x69ef6c7a
#9
0x69ef6c7b
#10
setData
#11
0x39435dac
#12
0x39435dac
· blocks 1
#13
0x39435dac
#15
0x09a2a2…bb02
#14
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
12
w0
14
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x310a7246…2dcb
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2905340c…dbc6
0x34b655…2a6f
3 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0d622e34…0000
0x681e90…ae09
2 touches
0 conflicts
0x00000000…0002
0xb857c1…9be1
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
0x310a7246ab…012dcb
Audit this contract →
← previous block
·
next block →
recent activity