pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,174,012
← previous block
next block →
recent activity
Analyzing
Block #76,174,012
13 transactions · 13 stateful · 2026-05-22 02:49:21 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,174,012
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
0xed82b078
#3
updatePrices
#4
0x98717539
#5
0x0c7abd22
#6
redeemDelegations
· blocks 1
#8
updateDataFeedsValuesPartial
#9
buy
#10
forward
#11
0xbf82f22b
#12
setData
#7
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0xabd6a3…49e4
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x33e6a77b…fa5a
0x065c9d…c394
2 touches
0 conflicts
0x514f7198…f4ae
0x065c9d…c394
2 touches
0 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
2 touches
0 conflicts
0x2f88a23f…9dc5
0x2a68ba…90c5
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:
0xabd6a35b…2649e4
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity