pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,638,687
← previous block
next block →
recent activity
Analyzing
Block #74,638,687
15 transactions · 11 stateful · 2026-05-14 23:55:15 UTC
Parallelism
80
/100
Blocked
18
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,638,687
· 15 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6a06615b
#2
0x6a06615b
#3
updatePrices
#4
transfer
· blocks 2
#7
transfer
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
0x0c7abd22
#11
0x6a06615b
#12
0xbe70473d
#13
setData
#14
0x39435dac
#5
transfer
· blocks 1
#6
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4e19ae4…0788
0xe7cd86…c82d
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
2 touches
0 conflicts
0x0d622e34…0000
0x681e90…ae09
2 touches
0 conflicts
0x3f35221b…d717
0x754704…b603
2 touches
0 conflicts
0x5e24c5e6…330d
0x754704…b603
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:
0xe7cd86e1…0fc82d
3 conflicts on slot
0xc4e19ae47e…dc0788
Audit this contract →
← previous block
·
next block →
recent activity