pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#77,784,767
← previous block
next block →
recent activity
Analyzing
Block #77,784,767
11 transactions · 10 stateful · 2026-05-29 13:41:05 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#77,784,767
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
updatePrices
#4
0x1a945f9c
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
buy
#8
execFwdPositionOps
#9
execFwdPositionOps
#10
setData
#2
0xab083028
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
0xb66fac10…85c2
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcedc9e30…a73f
0x065c9d…c394
3 touches
1 conflict
0x29d041b0…298f
0x065c9d…c394
2 touches
0 conflicts
0x42864472…2a41
0x065c9d…c394
2 touches
0 conflicts
0x50e763bf…5198
0x065c9d…c394
2 touches
0 conflicts
0x84c0dc28…48bc
0x065c9d…c394
2 touches
0 conflicts
0xce827910…ff22
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
0xb66fac10b9…7d85c2
Audit this contract →
← previous block
·
next block →
recent activity