pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,458,637
← previous block
next block →
recent activity
Analyzing
Block #72,458,637
7 transactions · 7 stateful · 2026-05-04 21:37:57 UTC
Parallelism
57
/100
Blocked
29
%
Avg conflicts / tx
0.43
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,458,637
· 7 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x3f5c179b
· blocks 2
#3
exactInputSingle
#6
setData
#4
0xed82b078
· blocks 1
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffe431af…8faa
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x0614abfc…5c45
0x065c9d…c394
2 touches
0 conflicts
0x1becc129…4390
0x065c9d…c394
2 touches
0 conflicts
0x3c075f28…fe50
0x065c9d…c394
2 touches
0 conflicts
0x6218280d…629c
0x065c9d…c394
2 touches
0 conflicts
0x8fb893e6…a352
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
0xffe431af56…838faa
Audit this contract →
← previous block
·
next block →
recent activity