pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,425,840
← previous block
next block →
recent activity
Analyzing
Block #74,425,840
13 transactions · 9 stateful · 2026-05-14 00:10:39 UTC
Parallelism
77
/100
Blocked
22
%
Avg conflicts / tx
0.15
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,425,840
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xa96df62f
#2
updatePrices
#3
updatePrices
#4
updatePrices
#5
updatePrices
#6
0x39435dac
· blocks 1
#7
redeemDelegations
#8
updateDataFeedsValuesPartial
#9
0x6a051377
#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
6
w0
11
w1
12
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb245fe36…d765
0x34b655…2a6f
4 touches
1 conflict
0xadac4a86…c2bc
0x34b655…2a6f
4 touches
1 conflict
0xd40bddc1…773c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x12fd91b6…cbe3
0x34b655…2a6f
2 touches
0 conflicts
0x85a88798…f85e
0x34b655…2a6f
2 touches
0 conflicts
0x8d13ecc1…980f
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0xb245fe3647…73d765
Audit this contract →
← previous block
·
next block →
recent activity