pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#73,416,417
← previous block
next block →
recent activity
Analyzing
Block #73,416,417
10 transactions · 9 stateful · 2026-05-09 07:55:13 UTC
Parallelism
60
/100
Blocked
33
%
Avg conflicts / tx
0.6
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,416,417
· 10 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x121eab2f
· blocks 3
#2
updateDataFeedsValuesPartial
#3
batchUpdate
#7
0xeffdedb0
#8
setData
#9
0xdc3f31…68cf
#4
batchUpdate
· blocks 2
#5
batchUpdate
· blocks 1
#6
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
5
w2
6
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0xf537eaa0…73c8
0x065c9d…c394
8 touches
6 conflicts
0x5bfd2e59…4fde
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x14a4ad11…ff04
0x065c9d…c394
2 touches
0 conflicts
0x6f08361d…bda6
0x065c9d…c394
2 touches
0 conflicts
0x9f512c52…b679
0x065c9d…c394
2 touches
0 conflicts
0xa91504f9…894f
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: MarginAccount
6 conflicts on slot
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity