pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,508,578
← previous block
next block →
recent activity
Analyzing
Block #74,508,578
9 transactions · 8 stateful · 2026-05-14 09:21:52 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,508,578
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
· blocks 1
#2
updatePrices
#3
updateDataFeedsValuesPartial
#5
0x6a0594a8
#6
setData
#7
0x39435dac
#8
0x39435dac
#4
0xc2d867a5
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33018431…8f5c
0x188d58…ea8e
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
4 touches
1 conflict
0x86644f36…7068
0x000000…012a
2 touches
0 conflicts
0xe069120c…952c
0x000000…012a
2 touches
0 conflicts
0x33018431…8f5d
0x188d58…ea8e
2 touches
0 conflicts
0x33018431…8f5e
0x188d58…ea8e
2 touches
0 conflicts
0x4aa4f53b…899f
0x188d58…ea8e
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:
0x188d586d…f9ea8e
1 conflict on slot
0x330184318b…418f5c
Audit this contract →
← previous block
·
next block →
recent activity