pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,394,501
← previous block
next block →
recent activity
Analyzing
Block #72,394,501
7 transactions · 5 stateful · 2026-05-04 14:30:33 UTC
Parallelism
71
/100
Blocked
20
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,394,501
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
updatePrices
#3
updatePrices
#4
updateDataFeedsValuesPartial
#6
setData
#5
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9ecf026…3b44
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9efdcfce…3195
0x065c9d…c394
3 touches
1 conflict
0xb452867c…8634
0x065c9d…c394
3 touches
1 conflict
0x24a83d8f…1712
0x065c9d…c394
2 touches
0 conflicts
0x3258ac13…a315
0x065c9d…c394
2 touches
0 conflicts
0x7edae8df…d3f5
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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
0xa9ecf0265f…cb3b44
Audit this contract →
← previous block
·
next block →
recent activity