pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,986,654
← previous block
next block →
recent activity
Analyzing
Block #70,986,654
13 transactions · 12 stateful · 2026-04-28 02:04:01 UTC
Parallelism
77
/100
Blocked
17
%
Avg conflicts / tx
0.23
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,986,654
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
swap
#3
updateDataFeedsValuesPartial
#4
relay
#5
0xed82b078
#6
0xed82b078
#7
0x69f01609
#8
setData
#9
updatePrices
· blocks 2
#10
updatePrices
#11
updatePrices
· blocks 1
#12
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
11
w1
12
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x8fd63a…536c
6 touches
3 conflicts
0x00000000…0001
0x8fd63a…536c
6 touches
3 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0xb857c1…9be1
2 touches
0 conflicts
0x62e20208…be65
0x0555e3…2b9c
2 touches
0 conflicts
0x846f2172…fd54
0x0555e3…2b9c
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
3 conflicts on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity