pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,042,263
← previous block
next block →
recent activity
Analyzing
Block #71,042,263
13 transactions · 11 stateful · 2026-04-28 08:14:11 UTC
Parallelism
77
/100
Blocked
18
%
Avg conflicts / tx
0.15
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,042,263
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x69f06ccb
#3
0x69f06ccb
#4
trade
#5
updatePrices
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#10
setData
#11
updatePrices
#12
updatePrices
#8
0x6463ffd1
· blocks 1
#9
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x07e439ca…de06
0x065c9d…c394
4 touches
1 conflict
0x127337a9…e227
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0xdbc8c9af…4f87
0x065c9d…c394
3 touches
1 conflict
0x195b30ca…50cb
0x065c9d…c394
3 touches
1 conflict
0x211e1069…7a50
0x065c9d…c394
3 touches
1 conflict
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:
0x2a68ba18…8e90c5
1 conflict on slot
0x92d610a6f9…379a40
Audit this contract →
← previous block
·
next block →
recent activity