pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,562,447
← previous block
next block →
recent activity
Analyzing
Block #74,562,447
8 transactions · 7 stateful · 2026-05-14 15:25:23 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,562,447
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x98717539
· blocks 1
#4
updateDataFeedsValuesPartial
#5
setData
#6
redeemDelegations
#7
0x39435dac
#3
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0x8d66a4…3095
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x40094141…7866
0x8d66a4…3095
3 touches
1 conflict
0x8a35acfb…d1a6
0x8d66a4…3095
3 touches
1 conflict
0x0711ec2d…d973
0x34b655…2a6f
2 touches
0 conflicts
0x085df2c1…305a
0x34b655…2a6f
2 touches
0 conflicts
0x1c389468…6b0e
0x34b655…2a6f
2 touches
0 conflicts
0x3c35979a…975d
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:
0x8d66a43f…113095
1 conflict on slot
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity