pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,696,452
← previous block
next block →
recent activity
Analyzing
Block #73,696,452
8 transactions · 8 stateful · 2026-05-10 15:04:30 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,696,452
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x121eab2f
· blocks 1
#2
swapAndStartBridgeTokensViaGasZip
#3
updateDataFeedsValuesPartial
#5
swap
#6
0x6a009ef5
#7
setData
#4
0x0c7abd22
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
0x11ddb141…a2a8
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x529acb6a…fcc6
0x065c9d…c394
4 touches
1 conflict
0xb9e69c06…ccfd
0x065c9d…c394
3 touches
1 conflict
0x0adf9c62…50fd
0x065c9d…c394
3 touches
1 conflict
0x7282eb4b…e0f0
0x065c9d…c394
2 touches
0 conflicts
0xab3a6ba2…3257
0x065c9d…c394
2 touches
0 conflicts
0xf792c5d2…f913
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
1 conflict on slot
0x11ddb14167…59a2a8
Audit this contract →
← previous block
·
next block →
recent activity