pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,172,394
← previous block
next block →
recent activity
Analyzing
Block #71,172,394
6 transactions · 5 stateful · 2026-04-28 22:40:57 UTC
Parallelism
67
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,172,394
· 6 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
setData
#3
0x6463ffd1
· blocks 1
#4
updatePosition
#5
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03b2f56d…1a03
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x9a10ba98…d286
0x065c9d…c394
4 touches
1 conflict
0xdf620278…4dc7
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x340ff8ac…1adc
0x065c9d…c394
4 touches
1 conflict
0xabd81ab2…0142
0x065c9d…c394
2 touches
1 conflict
0xcef06f6e…fb3f
0x065c9d…c394
2 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:
0x065c9d28…a9c394
1 conflict on slot
0x03b2f56ddb…d21a03
Audit this contract →
← previous block
·
next block →
recent activity