pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,036,208
← previous block
next block →
recent activity
Analyzing
Block #73,036,208
13 transactions · 7 stateful · 2026-05-07 13:45:30 UTC
Parallelism
85
/100
Blocked
14
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,036,208
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69fc97f2
· blocks 1
#3
updatePrices
#4
updatePrices
#5
updatePrices
#6
updatePrices
#7
updatePrices
#8
0x98717539
#9
updateDataFeedsValuesPartial
#10
setData
#11
redeemDelegations
#12
0xeffdedb0
#2
0x69fc97f2
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
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x20299510…1261
0x34b655…2a6f
2 touches
0 conflicts
0x20ac0567…c954
0x34b655…2a6f
2 touches
0 conflicts
0x2484cc15…5afc
0x34b655…2a6f
2 touches
0 conflicts
0x280d1119…ee4d
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