pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,222,542
← previous block
next block →
recent activity
Analyzing
Block #76,222,542
11 transactions · 11 stateful · 2026-05-22 08:12:21 UTC
Parallelism
73
/100
Blocked
18
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,222,542
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
transfer
#2
batchUpdate
#3
batchUpdate
· blocks 1
#5
batchUpdate
· blocks 1
#6
deposit
#7
redeemDelegations
#9
setData
#10
execOrders
#4
batchUpdate
· blocks 1
#8
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w0
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x3a6e7600…e1f1
0xa6afd3…d132
4 touches
1 conflict
0xdb9d8189…e926
0xa6afd3…d132
4 touches
1 conflict
0x9d2e313e…9db9
0x065c9d…c394
2 touches
0 conflicts
0xfc3f1f0c…dc3e
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0003
0x0c65a0…0852
2 touches
0 conflicts
0x2101a955…850f
0x0c65a0…0852
2 touches
0 conflicts
0x52c63247…ce02
0x0c65a0…0852
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
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity