pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,878,085
← previous block
next block →
recent activity
Analyzing
Block #70,878,085
15 transactions · 8 stateful · 2026-04-27 14:01:01 UTC
Parallelism
87
/100
Blocked
13
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,878,085
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69ef6c95
#2
updatePrices
#3
updatePrices
#4
updatePrices
#5
updatePrices
#6
updatePrices
#7
updatePrices
#8
0x98717539
#9
0x69ef6c95
#10
execute
#11
updateDataFeedsValuesPartial
#12
setData
#13
updatePrices
· blocks 1
#14
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
13
w0
14
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
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
0x313f2565…5b00
0x34b655…2a6f
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