pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,284,307
← previous block
next block →
recent activity
Analyzing
Block #71,284,307
9 transactions · 7 stateful · 2026-04-29 11:05:34 UTC
Parallelism
67
/100
Blocked
29
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,284,307
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
transfer
#3
0x98717539
· blocks 2
#5
updateDataFeedsValuesPartial
#6
updatePriceFeedsIfNecessary
#8
setData
#4
0x98717539
· blocks 1
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1ac
0x8d66a4…3095
4 touches
1 conflict
0xe89e1a22…ce49
0x8d66a4…3095
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x120121b8…b20c
0x065c9d…c394
2 touches
0 conflicts
0x41755291…977f
0x065c9d…c394
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:
0x34b6552d…112a6f
3 conflicts on slot
0x60f7fbaf90…97bd58
Audit this contract →
← previous block
·
next block →
recent activity