pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,399,784
← previous block
next block →
recent activity
Analyzing
Block #72,399,784
10 transactions · 9 stateful · 2026-05-04 15:05:47 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,399,784
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
updatePrices
#4
0x5bf9264c
#5
0x5bf9264c
#6
0x98717539
#7
updateDataFeedsValuesPartial
#9
setData
#2
0x0c7abd22
· blocks 1
#8
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcd444261…7841
0xd32edf…ff58
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x51ead586…3b5f
0x065c9d…c394
2 touches
0 conflicts
0x6549da7a…6602
0x065c9d…c394
2 touches
0 conflicts
0x912d3740…d136
0x065c9d…c394
2 touches
0 conflicts
0xb0084534…b41a
0x065c9d…c394
2 touches
0 conflicts
0xcbbd29e3…0c1a
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:
0x065c9d28…a9c394
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity