pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,920,965
← previous block
next block →
recent activity
Analyzing
Block #73,920,965
8 transactions · 7 stateful · 2026-05-11 16:09:22 UTC
Parallelism
63
/100
Blocked
29
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,920,965
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
addLiquidity
#2
0x98717539
· blocks 2
#5
updateDataFeedsValuesPartial
#6
0x6a01ffaa
#7
setData
#3
0x98717539
· blocks 1
#4
0x98717539
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
0xc6417de0…2191
0xc8689a…ee79
6 touches
3 conflicts
0x4f483049…3cc7
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
6 touches
3 conflicts
0x9be2b99a…a959
0x34b655…2a6f
6 touches
3 conflicts
0x9d652ee8…83ca
0x34b655…2a6f
6 touches
3 conflicts
0x9d92359d…0ca7
0x34b655…2a6f
6 touches
3 conflicts
0xac8e97a0…8426
0x34b655…2a6f
6 touches
3 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:
0xc8689a47…62ee79
3 conflicts on slot
0xc6417de023…802191
Audit this contract →
← previous block
·
next block →
recent activity