pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#73,479,044
← previous block
next block →
recent activity
Analyzing
Block #73,479,044
13 transactions · 11 stateful · 2026-05-09 14:51:53 UTC
Parallelism
77
/100
Blocked
18
%
Avg conflicts / tx
0.23
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,479,044
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
mint
#5
0x98717539
#6
forward
#7
batchUpdate
· blocks 2
#10
0x69ff4a81
#11
setData
#12
exactInputSingle
#8
batchUpdate
· blocks 1
#9
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xf537eaa0…73c8
0x065c9d…c394
4 touches
1 conflict
0x8b7e960c…a114
0x0555e3…2b9c
2 touches
0 conflicts
0xee0a9ebb…c425
0x0555e3…2b9c
2 touches
0 conflicts
0x00000000…0002
0x46a15b…4364
2 touches
0 conflicts
0x00000000…000d
0x46a15b…4364
2 touches
0 conflicts
0x668f537b…bbf9
0x46a15b…4364
2 touches
0 conflicts
0x5dfa485c…cf52
0x754704…b603
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: MarginAccount
3 conflicts on slot
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity