pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,484,255
← previous block
next block →
recent activity
Analyzing
Block #74,484,255
10 transactions · 8 stateful · 2026-05-14 06:39:27 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,484,255
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
#2
0x8263f5d9
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
redeemDelegations
· blocks 1
#6
forward
#7
setData
#9
0x39435dac
#8
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x1ccd9c…76ab
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1a36d156…c698
0x065c9d…c394
2 touches
0 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
2 touches
0 conflicts
0x968bdacb…f461
0x2a68ba…90c5
2 touches
0 conflicts
0x041ee703…b4c1
0x34b655…2a6f
2 touches
0 conflicts
0x04f0e47d…cb70
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:
0x1ccd9cad…8976ab
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity