pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,514,331
← previous block
next block →
recent activity
Analyzing
Block #74,514,331
8 transactions · 7 stateful · 2026-05-14 10:00:40 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,514,331
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1ffa3c9b
#2
updateDataFeedsValuesPartial
#3
0x6a059dc0
#4
0x785f5745
#5
setData
#6
redeemDelegations
· blocks 1
#7
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x04bdda…939b
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0dec7e8b…df6d
0x065c9d…c394
2 touches
0 conflicts
0x126c25d0…0a94
0x065c9d…c394
2 touches
0 conflicts
0x3d454d12…caf4
0x065c9d…c394
2 touches
0 conflicts
0x5919e8bd…3614
0x065c9d…c394
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:
0x04bdda56…52939b
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity