pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,845,996
← previous block
next block →
recent activity
Analyzing
Block #70,845,996
13 transactions · 10 stateful · 2026-04-27 10:27:15 UTC
Parallelism
85
/100
Blocked
20
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,845,996
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x6463ffd1
#5
setData
#6
0x69ef3a7b
#7
0x27ec65…c504
#8
0xc76318…8006
#9
updatePrices
· blocks 1
#10
updatePrices
· blocks 1
#11
updatePrices
#12
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w0
11
w1
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0x8fd63a…536c
4 touches
1 conflict
0x00000000…0000
0x8fd63a…536c
4 touches
1 conflict
0x00000000…0000
0xc1a578…8e1a
4 touches
1 conflict
0x00000000…0001
0xc1a578…8e1a
4 touches
1 conflict
0x27007746…0502
0x754704…b603
2 touches
0 conflicts
0xa3dc6f35…13e9
0x754704…b603
2 touches
0 conflicts
0x1ab875a8…5e58
0x8c5243…c33e
2 touches
0 conflicts
0x8956cb26…42f7
0x8c5243…c33e
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:
0x8fd63afb…2f536c
1 conflict on slot
0x0000000000…000001
Audit this contract →
← previous block
·
next block →
recent activity