pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#77,220,664
← previous block
next block →
recent activity
Analyzing
Block #77,220,664
6 transactions · 4 stateful · 2026-05-26 23:00:06 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#77,220,664
· 6 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
setData
#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
0x61434b99…5691
0x065c9d…c394
4 touches
1 conflict
0x2de2d8f9…738f
0x065c9d…c394
3 touches
1 conflict
0xe2ec28dc…1572
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x008cfebb…7412
0x065c9d…c394
2 touches
0 conflicts
0x36000e8c…ad34
0x065c9d…c394
2 touches
0 conflicts
0x47062d8a…52ff
0x065c9d…c394
2 touches
0 conflicts
0x77ed432f…fa04
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
0x61434b9922…045691
Audit this contract →
← previous block
·
next block →
recent activity