pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,256,423
← previous block
next block →
recent activity
Analyzing
Block #76,256,423
11 transactions · 6 stateful · 2026-05-22 11:58:10 UTC
Parallelism
82
/100
Blocked
17
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,256,423
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
#2
updateDataFeedsValuesPartial
#3
setData
#4
redeemDelegations
· blocks 1
#6
0xbe70473d
#7
0x9e76c652
#8
0x3e3800…b175
#9
0x4cd732…968d
#10
0x1ccf66…c1e3
#5
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0xc1b188…effd
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0006
0x2ab50b…5c41
2 touches
0 conflicts
0x012eafd7…5110
0x2ab50b…5c41
2 touches
0 conflicts
0x017130f6…f21c
0x2ab50b…5c41
2 touches
0 conflicts
0x0aae760d…1092
0x2ab50b…5c41
2 touches
0 conflicts
0x0adcc3cd…e165
0x2ab50b…5c41
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:
0xc1b188d4…86effd
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity