pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,399,807
← previous block
next block →
recent activity
Analyzing
Block #72,399,807
8 transactions · 6 stateful · 2026-05-04 15:05:56 UTC
Parallelism
63
/100
Blocked
33
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,399,807
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xcf7468f4
#2
0x0c7abd22
· blocks 1
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x69f8b64c
#3
0x0c7abd22
· blocks 1
#4
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ba1fda1…2acc
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd5f03365…a85f
0x065c9d…c394
3 touches
1 conflict
0xb584c967…d5fb
0x065c9d…c394
3 touches
1 conflict
0xb5f1a6f7…e930
0xd32edf…ff58
3 touches
1 conflict
0x97454acd…7653
0x065c9d…c394
2 touches
0 conflicts
0xba0fe99d…9243
0x065c9d…c394
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
0x4ba1fda142…212acc
Audit this contract →
← previous block
·
next block →
recent activity