pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,014,800
← previous block
next block →
recent activity
Analyzing
Block #73,014,800
9 transactions · 8 stateful · 2026-05-07 11:23:03 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,014,800
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x69fc768e
#4
0x69fc768e
#5
updateDataFeedsValuesPartial
#6
0xeffdedb0
#7
setData
#8
redeemDelegations
#3
0x121eab2f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b390c61…dc07
0x065c9d…c394
4 touches
1 conflict
0xb5e1ef4c…cd43
0x065c9d…c394
4 touches
1 conflict
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x568e39bf…db05
0x065c9d…c394
4 touches
1 conflict
0xc434dd11…3ff3
0x065c9d…c394
3 touches
1 conflict
0x38e5198e…766d
0x065c9d…c394
3 touches
1 conflict
0x97c93111…f8d1
0x065c9d…c394
3 touches
1 conflict
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x0b390c6160…02dc07
Audit this contract →
← previous block
·
next block →
recent activity