pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,668,540
← previous block
next block →
recent activity
Analyzing
Block #76,668,540
10 transactions · 10 stateful · 2026-05-24 09:42:10 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,668,540
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
execute302
#3
0xed82b078
#4
0x669a7d5e
#5
0x5339c59f
· blocks 1
#6
updateDataFeedsValuesPartial
#8
executeBatch
#9
setData
#7
0x62be7533
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xc28a8689…d1b3
0x000000…8ba3
2 touches
0 conflicts
0xd06cc746…27e4
0x0f34af…8b07
2 touches
0 conflicts
0x33f0fcd3…ae25
0x188d58…ea8e
2 touches
0 conflicts
0x847462fa…910f
0x188d58…ea8e
2 touches
0 conflicts
0xc50f72d2…4849
0x188d58…ea8e
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: MarginAccount
1 conflict on slot
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity