pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,444,188
← previous block
next block →
recent activity
Analyzing
Block #76,444,188
11 transactions · 10 stateful · 2026-05-23 08:48:17 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,444,188
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xff401d8f
· blocks 1
#3
revealWithCallback
#4
poke
#5
updateDataFeedsValuesPartial
#6
redeemDelegations
#7
0x0f6795d9
#8
0x0f6795d9
#9
0xe8891658
#10
setData
#2
0x1094dc9f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x46fd830b…81b5
0x065c9d…c394
4 touches
1 conflict
0x264c6e4e…cbb6
0x3bd359…433a
2 touches
0 conflicts
0x690117b9…2820
0x3bd359…433a
2 touches
0 conflicts
0xcb643582…2626
0x3bd359…433a
2 touches
0 conflicts
0xfe3bddd2…8b48
0x3bd359…433a
2 touches
0 conflicts
0xb0339ea9…b02e
0x754704…b603
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