pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,333,977
← previous block
next block →
recent activity
Analyzing
Block #74,333,977
15 transactions · 11 stateful · 2026-05-13 13:59:20 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,333,977
· 15 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
execute
#3
exactOutputSingle
#4
updatePrices
#5
updatePrices
#6
updatePrices
#7
0x98717539
· blocks 2
#10
updateDataFeedsValuesPartial
#11
setData
#12
approve
#13
0x6a048430
#14
0x39435dac
#8
0x98717539
· blocks 1
#9
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x10814d14…cdda
0x34b655…2a6f
4 touches
1 conflict
0x374426df…f445
0xc8689a…ee79
4 touches
1 conflict
0xa9988419…9f45
0x34b655…2a6f
4 touches
1 conflict
0xf1721ac7…b5f6
0x34b655…2a6f
4 touches
1 conflict
0xc852b267…9d14
0x34b655…2a6f
3 touches
1 conflict
0x7b43f938…3650
0x000000…012a
2 touches
0 conflicts
0x4dd1db39…a994
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:
Perpl
3 conflicts on slot
0x60f7fbaf90…97bd58
Audit this contract →
← previous block
·
next block →
recent activity