pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,476,280
← previous block
next block →
recent activity
Analyzing
Block #76,476,280
10 transactions · 10 stateful · 2026-05-23 12:21:58 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,476,280
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#2
redeemDelegations
#3
redeemDelegations
#6
0x5339c59f
#7
updateDataFeedsValuesPartial
#8
setData
#9
transfer
#4
0xab083028
· blocks 1
#5
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27a04273…27c5
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x3b126b58…1af4
0x065c9d…c394
3 touches
1 conflict
0xc6b7cfe3…97d5
0x065c9d…c394
3 touches
1 conflict
0x685bc3d0…c7c3
0x065c9d…c394
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
0x27a04273d4…7327c5
Audit this contract →
← previous block
·
next block →
recent activity