pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#72,497,785
← previous block
next block →
recent activity
Analyzing
Block #72,497,785
9 transactions · 6 stateful · 2026-05-05 01:58:30 UTC
Parallelism
67
/100
Blocked
33
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,497,785
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x719d975a
#2
0x0c7abd22
· blocks 2
#3
0x0f052239
#4
updatePrices
#7
updateDataFeedsValuesPartial
#8
setData
#5
0x0c7abd22
· blocks 1
#6
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xabe93bbf…0d5b
0xd32edf…ff58
5 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x120151…c1d6
2 touches
0 conflicts
0x00000000…0001
0x120151…c1d6
2 touches
0 conflicts
0x00000000…0003
0x120151…c1d6
2 touches
0 conflicts
0x00000000…0020
0x120151…c1d6
2 touches
0 conflicts
0x3c6f84da…5ac3
0x188d58…ea8e
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
3 conflicts on slot
0xabe93bbf0f…140d5b
Audit this contract →
← previous block
·
next block →
recent activity