pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,065,515
← previous block
next block →
recent activity
Analyzing
Block #71,065,515
9 transactions · 7 stateful · 2026-04-28 10:48:58 UTC
Parallelism
67
/100
Blocked
29
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,065,515
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#2
execute
#3
updatePrices
#4
updateDataFeedsValuesPartial
#7
0x69f09112
#8
setData
#5
0x6463ffd1
· blocks 1
#6
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x19e4b82d…f372
0x065c9d…c394
4 touches
1 conflict
0xa1d927ba…7c56
0x065c9d…c394
4 touches
1 conflict
0xac0a8f7f…d4d5
0x065c9d…c394
4 touches
1 conflict
0xc3cd970c…7369
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
3 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity