pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,094,942
← previous block
next block →
recent activity
Analyzing
Block #71,094,942
10 transactions · 9 stateful · 2026-04-28 14:05:07 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,094,942
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69f0bf0a
#2
0x69f0bf0a
#3
0xb3dd4ec4
#4
updatePrices
#5
0x98717539
#6
updateDataFeedsValuesPartial
#7
0x6463ffd1
· blocks 1
#9
setData
#8
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a8a1ed6…e2a5
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0xaf98ee75…69e1
0x065c9d…c394
3 touches
1 conflict
0xb2b89bff…e439
0x065c9d…c394
3 touches
1 conflict
0xf723ec04…5ef7
0x065c9d…c394
3 touches
1 conflict
0x8956cb26…42fa
0x73ada1…8be0
2 touches
0 conflicts
0x8956cb26…42fd
0x73ada1…8be0
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
0x0a8a1ed618…7ce2a5
Audit this contract →
← previous block
·
next block →
recent activity