pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,505,264
← previous block
next block →
recent activity
Analyzing
Block #73,505,264
5 transactions · 4 stateful · 2026-05-09 17:46:31 UTC
Parallelism
60
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,505,264
· 5 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
updateDataFeedsValuesPartial
#4
setData
#2
0x121eab2f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x033df367…6b65
0x065c9d…c394
2 touches
0 conflicts
0x06161458…e6eb
0x065c9d…c394
2 touches
0 conflicts
0x159faca1…491d
0x065c9d…c394
2 touches
0 conflicts
0x1e88f8f8…efb1
0x065c9d…c394
2 touches
0 conflicts
0x38f21af7…0dd2
0x065c9d…c394
2 touches
0 conflicts
0x8e11c899…c473
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity