pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,441,389
← previous block
next block →
recent activity
Analyzing
Block #74,441,389
12 transactions · 11 stateful · 2026-05-14 01:54:12 UTC
Parallelism
75
/100
Blocked
18
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,441,389
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xa96df62f
#2
0x1ffa3c9b
· blocks 2
#4
updatePrices
#5
redeemDelegations
#6
redeemDelegations
#7
updateDataFeedsValuesPartial
#9
0x6a052bbc
#10
setData
#11
0x39435dac
#3
0xed82b078
· blocks 1
#8
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x08b86375…a3a0
0x065c9d…c394
2 touches
0 conflicts
0x5b9804ba…d351
0x065c9d…c394
2 touches
0 conflicts
0x9714cea8…dead
0x065c9d…c394
2 touches
0 conflicts
0x9b5b79b9…17e8
0x065c9d…c394
2 touches
0 conflicts
0xdda897b6…b0a8
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
3 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity