pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,996,617
← previous block
next block →
recent activity
Analyzing
Block #70,996,617
12 transactions · 11 stateful · 2026-04-28 03:10:24 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,996,617
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xb264ae19
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
0x6463ffd1
· blocks 1
#6
0x0c7abd22
#7
0x69f02597
#8
setData
#9
0x39435dac
#10
updatePrices
#11
updatePrices
#5
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x19ed8762…a8b7
0x065c9d…c394
4 touches
1 conflict
0x1c601885…a733
0x065c9d…c394
4 touches
1 conflict
0x4f2e57a8…9769
0x065c9d…c394
4 touches
1 conflict
0xe5796bab…1b0d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
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:
0x065c9d28…a9c394
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity