pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#77,183,932
← previous block
next block →
recent activity
Analyzing
Block #77,183,932
14 transactions · 10 stateful · 2026-05-26 18:53:23 UTC
Parallelism
86
/100
Blocked
10
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#77,183,932
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x6a15ec9b
#3
batchUpdate
#5
batchUpdate
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x3f5c179b
#9
execFwdPositionOps
#10
execFwdPositionOps
#11
forward
#12
0x6a15ec9a
#13
setData
#4
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x77ed432f…fa04
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
0x18eaef66…80b4
0x065c9d…c394
2 touches
0 conflicts
0x237765d0…1764
0x065c9d…c394
2 touches
0 conflicts
0x6a0bf516…05f6
0x065c9d…c394
2 touches
0 conflicts
0xaf82d90a…0c12
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
0x77ed432f03…d6fa04
Audit this contract →
← previous block
·
next block →
recent activity