pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#81,632,012
← previous block
next block →
recent activity
Analyzing
Block #81,632,012
11 transactions · 9 stateful · 2026-06-16 09:25:45 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#81,632,012
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x23afbff3
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
updatePrices
#5
redeemDelegations
#6
setData
#7
0xa09e9040
· blocks 1
#9
0x3f5c179b
#10
0x2c5982…b291
#8
0x23afbff3
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8dd03ce…dc8d
0x2a68ba…90c5
4 touches
1 conflict
0xee408588…38ba
0x065c9d…c394
4 touches
1 conflict
0x14f58fd2…bd16
0x065c9d…c394
3 touches
1 conflict
0x3421a92c…b0bc
0x065c9d…c394
3 touches
1 conflict
0x101cc018…9c9f
0x065c9d…c394
2 touches
0 conflicts
0x7d9847c2…90ab
0x065c9d…c394
2 touches
0 conflicts
0xb7171f05…a0d5
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0002
0x1c8a33…d316
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
0xd8dd03ce37…9cdc8d
Audit this contract →
← previous block
·
next block →
recent activity