pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,393,920
← previous block
next block →
recent activity
Analyzing
Block #73,393,920
7 transactions · 6 stateful · 2026-05-09 05:25:24 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,393,920
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
modifyLiquidities
#3
0x5339c59f
· blocks 1
#5
0x69fec5bc
#6
setData
#4
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x22e295f5…1bef
0x065c9d…c394
2 touches
0 conflicts
0x6bdeafc0…28e3
0x065c9d…c394
2 touches
0 conflicts
0x7adb2633…0dff
0x065c9d…c394
2 touches
0 conflicts
0x3555d21c…7d22
0x188d58…ea8e
2 touches
0 conflicts
0x99845708…8e6b
0x188d58…ea8e
2 touches
0 conflicts
0xb9c32323…0208
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity