pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,227,412
← previous block
next block →
recent activity
Analyzing
Block #76,227,412
12 transactions · 8 stateful · 2026-05-22 08:45:01 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,227,412
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
redeemDelegations
#6
executeBatch
#7
setData
#8
0xa9aba3…4d88
#9
0xb13b93…fc3f
#10
0x4a4e51…37a7
#11
approve
#2
batchUpdate
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
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x435f1d5d…daca
0x065c9d…c394
2 touches
0 conflicts
0x530bb918…59ec
0x065c9d…c394
2 touches
0 conflicts
0x64b55394…87f2
0x065c9d…c394
2 touches
0 conflicts
0xd96a1ce6…b0e0
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
0xfe2bac2b2f…482cec
Audit this contract →
← previous block
·
next block →
recent activity