pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,664,226
← previous block
next block →
recent activity
Analyzing
Block #73,664,226
10 transactions · 9 stateful · 2026-05-10 11:27:00 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,664,226
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6a006bfc
#2
updatePrices
#3
0x121eab2f
· blocks 2
#4
0x98717539
#5
updateDataFeedsValuesPartial
#6
setData
#7
closeTrade
#8
0xed82b078
· blocks 1
#9
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f81fb82…633e
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x326738be…4c88
0x065c9d…c394
2 touches
0 conflicts
0x3375b544…76dd
0x065c9d…c394
2 touches
0 conflicts
0x6c4fa36f…769f
0x065c9d…c394
2 touches
0 conflicts
0xaedac35c…4557
0x065c9d…c394
2 touches
0 conflicts
0xb159af88…a9e7
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:
0x065c9d28…a9c394
3 conflicts on slot
0x7f81fb82c1…ec633e
Audit this contract →
← previous block
·
next block →
recent activity