pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,995,506
← previous block
next block →
recent activity
Analyzing
Block #70,995,506
12 transactions · 11 stateful · 2026-04-28 03:03:00 UTC
Parallelism
75
/100
Blocked
27
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,995,506
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
transfer
#2
updatePrices
· blocks 2
#5
updateDataFeedsValuesPartial
#6
0x6463ffd1
#7
modifyLiquidities
#8
0xed82b078
· blocks 1
#10
0x69f023dc
#11
setData
#3
updatePrices
· blocks 1
#9
0xed82b078
#4
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb857c1…9be1
6 touches
3 conflicts
0x00000000…003d
0x131a2e…0da9
4 touches
1 conflict
0x5c8c6ab6…dc36
0x131a2e…0da9
4 touches
1 conflict
0x4ab14837…e1b2
0x2a68ba…90c5
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
0xb374d549…5e5e
0x754704…b603
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:
0xb857c13a…1a9be1
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity