pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,726,860
← previous block
next block →
recent activity
Analyzing
Block #74,726,860
7 transactions · 5 stateful · 2026-05-15 09:43:26 UTC
Parallelism
71
/100
Blocked
20
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,726,860
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x98717539
· blocks 1
#3
redeemDelegations
#4
redeemDelegations
#5
setData
#6
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfdcf4626…a99e
0x34b655…2a6f
4 touches
1 conflict
0x801a6e57…d85c
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x00456f78…2b80
0x34b655…2a6f
4 touches
1 conflict
0x2233f38c…0d84
0x34b655…2a6f
2 touches
0 conflicts
0x23114fac…630a
0x34b655…2a6f
2 touches
0 conflicts
0x309ef367…e8a1
0x34b655…2a6f
2 touches
0 conflicts
0x32454f9f…67d2
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
0xfdcf4626fb…dca99e
Audit this contract →
← previous block
·
next block →
recent activity