pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,563,265
← previous block
next block →
recent activity
Analyzing
Block #74,563,265
14 transactions · 9 stateful · 2026-05-14 15:30:53 UTC
Parallelism
86
/100
Blocked
11
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,563,265
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1ffa3c9b
· blocks 1
#3
updatePrices
#4
updatePrices
#5
0x98717539
#6
0x98717539
#7
redeemDelegations
#8
updateDataFeedsValuesPartial
#9
0x6a05eb25
#10
approve
#11
setData
#12
0x3a84c6…19ae
#13
redeemDelegations
#2
0xed82b078
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
0xef715e05…6a10
0x065c9d…c394
3 touches
1 conflict
0xfa095176…f9a0
0x065c9d…c394
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x427d2551…f465
0x065c9d…c394
2 touches
0 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
2 touches
0 conflicts
0x6ddd6f49…59b8
0x065c9d…c394
2 touches
0 conflicts
0x7ae22077…e5f2
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: Market-MON/USDC
1 conflict on slot
0xef715e0599…786a10
Audit this contract →
← previous block
·
next block →
recent activity