pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,495,975
← previous block
next block →
recent activity
Analyzing
Block #76,495,975
8 transactions · 8 stateful · 2026-05-23 14:33:11 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,495,975
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1094dc9f
#2
0xab083028
· blocks 1
#3
updateDataFeedsValuesPartial
#5
redeemDelegations
#6
setData
#7
redeemDelegations
#4
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xcc6434bd…6d5c
0xa6afd3…d132
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3833c9c9…14dd
0x1111b3…4111
2 touches
0 conflicts
0xb3eae1cb…7249
0x1111b3…4111
2 touches
0 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
2 touches
0 conflicts
0xa1087a5c…66c4
0x754704…b603
2 touches
0 conflicts
0xe782fcdb…edef
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:
0xa6afd386…b0d132
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity