pev
.
One block, wave by wave
→
analytics
docs
offline
by Silk Nodes →
pev
/
block
/
#73,501,385
← previous block
next block →
recent activity
Analyzing
Block #73,501,385
10 transactions · 10 stateful · 2026-05-09 17:20:37 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,501,385
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x69ff6d5c
· blocks 2
#2
updatePrices
#4
0x121eab2f
#5
0x98717539
#6
updateDataFeedsValuesPartial
#7
modifyLiquidities
#9
setData
#3
0x69ff6d5c
· blocks 1
#8
0x69ff6d5c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x42a1f859…c5fc
0x065c9d…c394
2 touches
0 conflicts
0x98c463b9…fbd6
0x065c9d…c394
2 touches
0 conflicts
0xae429334…4648
0x065c9d…c394
2 touches
0 conflicts
0xafb55b80…f54d
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:
0x681e908b…e1ae09
3 conflicts on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity