pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,976,029
← previous block
next block →
recent activity
Analyzing
Block #72,976,029
9 transactions · 6 stateful · 2026-05-07 07:04:58 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,976,029
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xcf7468f4
#2
0xb264ae19
#3
0x0c7abd22
· blocks 1
#4
updateDataFeedsValuesPartial
#6
0xeffdedb0
#7
setData
#8
0x39435dac
#5
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9753eb1…f00f
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x47c1a8e8…f74a
0x34b655…2a6f
2 touches
0 conflicts
0x7cee1be1…e770
0x34b655…2a6f
2 touches
0 conflicts
0x9e719c7a…df63
0x34b655…2a6f
2 touches
0 conflicts
0xb91a6f59…722c
0x34b655…2a6f
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:
0xd32edf66…9fff58
1 conflict on slot
0xd9753eb12f…e1f00f
Audit this contract →
← previous block
·
next block →
recent activity