pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,463,077
← previous block
next block →
recent activity
Analyzing
Block #74,463,077
10 transactions · 6 stateful · 2026-05-14 04:18:36 UTC
Parallelism
80
/100
Blocked
17
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,463,077
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x39435dac
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0xafd222…1a5e
#5
setData
#6
0xf1e401…d730
#7
0xa49e5a…e930
#8
redeemDelegations
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c389468…6b0e
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x116a621e…f97f
0x34b655…2a6f
2 touches
0 conflicts
0x3d6ad949…c225
0x34b655…2a6f
2 touches
0 conflicts
0x4d63bc0a…65d8
0x34b655…2a6f
2 touches
0 conflicts
0x4ee6f153…3ef4
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
0x1c38946843…a16b0e
Audit this contract →
← previous block
·
next block →
recent activity