pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,271,552
← previous block
next block →
recent activity
Analyzing
Block #72,271,552
10 transactions · 7 stateful · 2026-05-04 00:50:02 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,271,552
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x3f5c179b
· blocks 1
#2
0x0c7abd22
#3
relay
#4
relay
#6
updateDataFeedsValuesPartial
#7
0xe442d8…d5e3
#8
0xe5087e…cd63
#9
setData
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x08073057…5069
0x065c9d…c394
2 touches
0 conflicts
0x379cf9a8…f0fa
0x065c9d…c394
2 touches
0 conflicts
0x62f52ece…d37d
0x065c9d…c394
2 touches
0 conflicts
0x658edd39…3c5c
0x065c9d…c394
2 touches
0 conflicts
0x800ff46b…ccce
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