pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,065,252
← previous block
next block →
recent activity
Analyzing
Block #71,065,252
11 transactions · 11 stateful · 2026-04-28 10:47:13 UTC
Parallelism
73
/100
Blocked
18
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,065,252
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x98717539
#3
0x6463ffd1
· blocks 2
#6
forward
#7
forward
#8
updateDataFeedsValuesPartial
#9
setData
#10
approve
#4
0x6463ffd1
· blocks 1
#5
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ff9e831…6008
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x64684f9d…b878
0x065c9d…c394
5 touches
3 conflicts
0x10b5ff2e…ea9b
0x065c9d…c394
4 touches
1 conflict
0xb17ed949…fec4
0x065c9d…c394
4 touches
1 conflict
0xa791b18e…7a7b
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0xbdb8fe12…d2ad
0x065c9d…c394
4 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
3 conflicts on slot
0x5ff9e83175…0f6008
Audit this contract →
← previous block
·
next block →
recent activity