pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,680,410
← previous block
next block →
recent activity
Analyzing
Block #73,680,410
13 transactions · 8 stateful · 2026-05-10 13:16:25 UTC
Parallelism
85
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,680,410
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a0085a1
· blocks 1
#3
0x6a0085a1
#4
updatePrices
#5
updatePrices
#6
0x39435dac
#7
redeemDelegations
#8
0x0c7abd22
#9
updateDataFeedsValuesPartial
#10
updateDataFeedsValuesPartial
#11
0x6a0085a1
#12
setData
#2
0x6a0085a1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x15652b2f…0889
0x065c9d…c394
2 touches
0 conflicts
0x005bcc9d…5141
0x34b655…2a6f
2 touches
0 conflicts
0x19a745e4…205a
0x34b655…2a6f
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
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
1 conflict on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity