pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,915,153
← previous block
next block →
recent activity
Analyzing
Block #74,915,153
13 transactions · 12 stateful · 2026-05-16 06:40:24 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
#74,915,153
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5bf9264c
#3
execute
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
redeemDelegations
#7
updatePriceFeedsIfNecessary
#8
forward
#9
0x6a0811d0
#10
setData
#11
0x39435dac
· blocks 1
#12
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94710b77…a921
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3f1434d4…1ce1
0x11ed3b…2c96
2 touches
0 conflicts
0x00000000…0000
0x2d59fc…cd50
2 touches
0 conflicts
0x00000000…0003
0x2d59fc…cd50
2 touches
0 conflicts
0x00000000…0004
0x2d59fc…cd50
2 touches
0 conflicts
0x00000000…0009
0x2d59fc…cd50
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:
0x34b6552d…112a6f
1 conflict on slot
0x94710b77de…eca921
Audit this contract →
← previous block
·
next block →
recent activity