pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,398,635
← previous block
next block →
recent activity
Analyzing
Block #73,398,635
9 transactions · 9 stateful · 2026-05-09 05:56:52 UTC
Parallelism
56
/100
Blocked
33
%
Avg conflicts / tx
0.67
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,398,635
· 9 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
0x121eab2f
· blocks 3
#7
0x69fecd1c
#8
setData
#4
0x5339c59f
· blocks 2
#5
0xed82b078
· blocks 1
#6
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
6
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xbdb35945…e93f
0x065c9d…c394
4 touches
1 conflict
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
0xcd626f8b…12af
0x065c9d…c394
3 touches
1 conflict
0x467975f3…d180
0x065c9d…c394
3 touches
1 conflict
0x1caca7ff…d0e1
0x065c9d…c394
3 touches
1 conflict
0x03f07c0b…6578
0x065c9d…c394
3 touches
1 conflict
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
3 conflicts on slot
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity