pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,996,044
← previous block
next block →
recent activity
Analyzing
Block #70,996,044
10 transactions · 9 stateful · 2026-04-28 03:06:35 UTC
Parallelism
70
/100
Blocked
33
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,996,044
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
· blocks 2
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x6463ffd1
· blocks 1
#8
forward
#9
setData
#2
updatePrices
· blocks 1
#7
0x6463ffd1
#3
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
6
w0
7
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
0x065c9d…c394
4 touches
1 conflict
0x28e59e33…0ce6
0x065c9d…c394
4 touches
1 conflict
0x449de693…e03c
0x065c9d…c394
4 touches
1 conflict
0x751eb745…29ff
0x065c9d…c394
4 touches
1 conflict
0xe7e7fd3f…455c
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x09000000…0001
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:
0xb857c13a…1a9be1
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity