pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,037,215
← previous block
next block →
recent activity
Analyzing
Block #71,037,215
9 transactions · 7 stateful · 2026-04-28 07:40:35 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,037,215
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x69f064eb
#3
updateDataFeedsValuesPartial
#4
0x0c7abd22
· blocks 1
#6
setData
#7
updatePrices
#8
updatePrices
#5
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb87
0x1b6862…e19c
4 touches
1 conflict
0xf9ba7024…3d7b
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0001
0x010592…1c83
2 touches
0 conflicts
0x00000000…0006
0x010592…1c83
2 touches
0 conflicts
0x52bbd74a…3b5c
0x010592…1c83
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:
0x1b68626d…2de19c
1 conflict on slot
0xd9f18d9a4a…7f141d
Audit this contract →
← previous block
·
next block →
recent activity