pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,400,307
← previous block
next block →
recent activity
Analyzing
Block #72,400,307
9 transactions · 8 stateful · 2026-05-04 15:09:16 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,400,307
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x9036287a
· blocks 2
#2
0x1a945f9c
#5
modifyLiquidities
#6
updateDataFeedsValuesPartial
#7
0x69f8b714
#8
setData
#3
0x0c7abd22
· blocks 1
#4
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46adc421…4ad0
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x46151ee5…9cdd
0x065c9d…c394
5 touches
3 conflicts
0x65e4e374…d81a
0x065c9d…c394
5 touches
3 conflicts
0xe8248717…10af
0x065c9d…c394
3 touches
1 conflict
0x661cdc8c…6ee1
0x065c9d…c394
2 touches
0 conflicts
0xbbee74c2…567a
0x065c9d…c394
2 touches
0 conflicts
0xeb4ba6d9…4dee
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
3 conflicts on slot
0x46adc4217f…2b4ad0
Audit this contract →
← previous block
·
next block →
recent activity