pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,065,213
← previous block
next block →
recent activity
Analyzing
Block #71,065,213
11 transactions · 9 stateful · 2026-04-28 10:46:57 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,065,213
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
updatePrices
#3
updatePrices
#4
0x69f09099
#5
0x6463ffd1
· blocks 1
#6
updateDataFeedsValuesPartial
#7
updatePriceFeedsIfNecessary
#9
setData
#10
approve
#8
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ff9e831…6008
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x57736090…5208
0x065c9d…c394
3 touches
1 conflict
0x90f081c4…2970
0x065c9d…c394
3 touches
1 conflict
0x3bc196e1…2d8b
0x73ada1…8be0
2 touches
0 conflicts
0x85c47f74…2235
0x73ada1…8be0
2 touches
0 conflicts
0x8956cb26…42f7
0x73ada1…8be0
2 touches
0 conflicts
0x8956cb26…42fa
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
0x5ff9e83175…0f6008
Audit this contract →
← previous block
·
next block →
recent activity