pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,211,001
← previous block
next block →
recent activity
Analyzing
Block #73,211,001
11 transactions · 10 stateful · 2026-05-08 09:08:31 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,211,001
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
updatePrices
#3
0x39435dac
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x69fda887
#9
0xeffdedb0
#10
0x39435dac
#4
0x121eab2f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa79eb258…9183
0x065c9d…c394
4 touches
1 conflict
0x61337b97…e0ff
0x065c9d…c394
4 touches
1 conflict
0x64979bde…ba46
0x065c9d…c394
4 touches
1 conflict
0x0d60acdd…b8a4
0x065c9d…c394
4 touches
1 conflict
0x4210b32c…d21b
0x065c9d…c394
3 touches
1 conflict
0xea1baab3…529d
0x065c9d…c394
3 touches
1 conflict
0xaa112af8…b6f2
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity