pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,566,007
← previous block
next block →
recent activity
Analyzing
Block #74,566,007
12 transactions · 10 stateful · 2026-05-14 15:49:19 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,566,007
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
redeemDelegations
#4
0x0f6795d9
#5
0x0f6795d9
#6
updateDataFeedsValuesPartial
#7
updateTemporalNumericValuesV1
#8
forward
#9
setData
#10
0x39435dac
· blocks 1
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x11d05707…3e30
0x34b655…2a6f
2 touches
0 conflicts
0x44f26cbe…58c2
0x34b655…2a6f
2 touches
0 conflicts
0x71e4ffd1…9beb
0x34b655…2a6f
2 touches
0 conflicts
0x967123a1…901f
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
0x83f3d32000…25fb59
Audit this contract →
← previous block
·
next block →
recent activity