pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,432,658
← previous block
next block →
recent activity
Analyzing
Block #74,432,658
11 transactions · 11 stateful · 2026-05-14 00:56:06 UTC
Parallelism
73
/100
Blocked
18
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,432,658
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#4
0x0000a099
#5
0x6df9e92b
#6
redeemDelegations
#7
0x39435dac
#8
updateDataFeedsValuesPartial
#9
0x6a051e1d
#10
setData
#2
0xed82b078
· blocks 1
#3
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xbbee74c2…567a
0x065c9d…c394
4 touches
1 conflict
0x8adc5ee8…0d73
0x065c9d…c394
3 touches
1 conflict
0x408e57fb…fdff
0x065c9d…c394
3 touches
1 conflict
0xacc3e6f0…bef7
0x065c9d…c394
2 touches
0 conflicts
0xd5f04c38…3ff1
0x065c9d…c394
2 touches
0 conflicts
0xed56e4da…baa5
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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