pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,678,958
← previous block
next block →
recent activity
Analyzing
Block #76,678,958
12 transactions · 10 stateful · 2026-05-24 10:51:35 UTC
Parallelism
75
/100
Blocked
30
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,678,958
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
· blocks 2
#4
handleOps
#5
0x5bf9264c
#6
0x5bf9264c
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
setData
#11
0x39435dac
#2
0xab083028
· blocks 2
#3
0xab083028
#7
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99a21305…dffc
0x2a68ba…90c5
6 touches
3 conflicts
0x1fff6dcb…b3f4
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xaf59b8c6…8ef6
0x065c9d…c394
4 touches
1 conflict
0x06e40499…165e
0x1d1325…2305
4 touches
1 conflict
0xa17ec269…7cdd
0x1d1325…2305
4 touches
1 conflict
0xa605468c…1bfc
0x1d1325…2305
4 touches
1 conflict
0xc8525006…2b45
0x1d1325…2305
4 touches
1 conflict
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: MarginAccount
3 conflicts on slot
0x99a2130578…57dffc
Audit this contract →
← previous block
·
next block →
recent activity