pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,414,210
← previous block
next block →
recent activity
Analyzing
Block #76,414,210
15 transactions · 7 stateful · 2026-05-23 05:28:54 UTC
Parallelism
87
/100
Blocked
14
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,414,210
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
#2
updatePrices
#3
updatePrices
#4
updatePrices
#5
updatePrices
#6
updatePrices
#7
updatePrices
#8
updatePrices
#9
redeemDelegations
· blocks 1
#10
forward
#11
updateDataFeedsValuesPartial
#12
0x994035…8351
#13
setData
#14
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
14
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0xe2ef26…cc1c
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x8be5d4bc…5c5d
0x065c9d…c394
2 touches
0 conflicts
0x2f88a23f…9dc5
0x2a68ba…90c5
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
2 touches
0 conflicts
0x68faa0b9…14af
0x368ee5…7ca4
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:
0xe2ef26ef…00cc1c
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity