pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,744,764
← previous block
next block →
recent activity
Analyzing
Block #73,744,764
9 transactions · 8 stateful · 2026-05-10 20:30:33 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
#73,744,764
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#4
updatePosition
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x39435dac
#2
0x76368669
· blocks 1
#3
0xccf50a51
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x529acb6a…fcc6
0x065c9d…c394
4 touches
1 conflict
0xe75ce681…ba5f
0x188d58…ea8e
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xe75ce681…ba61
0x188d58…ea8e
4 touches
1 conflict
0xfac61869…a560
0x1b6862…e19c
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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:
USDC (USDC)
3 conflicts on slot
0xa1087a5ca6…0a66c4
Audit this contract →
← previous block
·
next block →
recent activity