pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,030,011
← previous block
next block →
recent activity
Analyzing
Block #73,030,011
11 transactions · 8 stateful · 2026-05-07 13:04:15 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,030,011
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xcf7468f4
· blocks 1
#2
updateDataFeedsValuesPartial
#4
0x0c7abd22
#5
exactInputSingle
#6
0x62be7533
#7
0x39435dac
#8
0x69fc8e47
#9
0xeffdedb0
#10
setData
#3
0x121eab2f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe09eda07…8dda
0x2a68ba…90c5
4 touches
1 conflict
0xf0c981f3…117e
0x065c9d…c394
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0b390c61…dc07
0x065c9d…c394
2 touches
0 conflicts
0x2a4a5d49…518e
0x065c9d…c394
2 touches
0 conflicts
0x3686ab05…44bb
0x065c9d…c394
2 touches
0 conflicts
0x55de393b…ba92
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: MarginAccount
1 conflict on slot
0xe09eda075e…748dda
Audit this contract →
← previous block
·
next block →
recent activity