pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,042,220
← previous block
next block →
recent activity
Analyzing
Block #71,042,220
10 transactions · 9 stateful · 2026-04-28 08:13:54 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,042,220
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x69f06cb9
#4
updatePrices
#5
0xe7be4706
#6
0xe7be4706
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x39435dac
#2
0xcf7468f4
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8bc71ff1…9c7d
0x065c9d…c394
4 touches
1 conflict
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0x6af306bb…2e81
0x3bd359…433a
4 touches
1 conflict
0x1c354dc0…96de
0x754704…b603
4 touches
1 conflict
0x943bf267…fd17
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xf91b744e…9117
0x754704…b603
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:
0x065c9d28…a9c394
1 conflict on slot
0x8bc71ff126…2d9c7d
Audit this contract →
← previous block
·
next block →
recent activity