pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,995,349
← previous block
next block →
recent activity
Analyzing
Block #70,995,349
15 transactions · 12 stateful · 2026-04-28 03:01:57 UTC
Parallelism
87
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,995,349
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execute_route
#3
0xa96df62f
#4
0x69f0239d
#5
updatePrices
#6
updatePrices
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
0x6463ffd1
#10
0x69f0239d
#11
setData
#12
updatePrices
#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
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001e
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002e
0x1b6862…e19c
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