pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#72,994,203
← previous block
next block →
recent activity
Analyzing
Block #72,994,203
8 transactions · 7 stateful · 2026-05-07 09:06:07 UTC
Parallelism
75
/100
Blocked
29
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,994,203
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x121eab2f
· blocks 2
#2
updateDataFeedsValuesPartial
#3
redeemDelegations
#6
0xeffdedb0
#7
setData
#4
0x0c7abd22
#5
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c87a09d…c5b4
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8947b4ee…3778
0x065c9d…c394
4 touches
1 conflict
0x84279c46…696f
0x065c9d…c394
3 touches
1 conflict
0x71f61ac2…d197
0x065c9d…c394
3 touches
1 conflict
0xa02c90a7…2965
0x065c9d…c394
3 touches
1 conflict
0x05f292c9…3e2a
0x065c9d…c394
3 touches
1 conflict
0xbd7e37a9…9eb5
0x065c9d…c394
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
0x4c87a09d55…58c5b4
Audit this contract →
← previous block
·
next block →
recent activity