pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,176,122
← previous block
next block →
recent activity
Analyzing
Block #73,176,122
12 transactions · 7 stateful · 2026-05-08 05:16:16 UTC
Parallelism
83
/100
Blocked
14
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,176,122
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x98717539
#3
updateDataFeedsValuesPartial
#4
0x0c7abd22
· blocks 1
#6
0xed82b078
#7
0xed82b078
#8
0xeffdedb0
#9
setData
#10
0x36326531
#11
exactInputSingle
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e66da19…66b6
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x269ac632…c27d
0x065c9d…c394
2 touches
0 conflicts
0x7603227c…8c9c
0x065c9d…c394
2 touches
0 conflicts
0xa0f4d35f…f1ae
0x065c9d…c394
2 touches
0 conflicts
0xc314c5ee…ab39
0x065c9d…c394
2 touches
0 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
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
1 conflict on slot
0x8e66da1932…c966b6
Audit this contract →
← previous block
·
next block →
recent activity