pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,918,619
← previous block
next block →
recent activity
Analyzing
Block #74,918,619
16 transactions · 13 stateful · 2026-05-16 07:03:32 UTC
Parallelism
88
/100
Blocked
8
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,918,619
· 16 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xce1e7030
#3
0x6a08173c
· blocks 1
#4
updatePrices
#5
updatePrices
#7
updateDataFeedsValuesPartial
#8
0x6a08173b
#9
0x6a08173b
#10
0x98717539
#11
exactInputSingle
#12
0x5339c59f
#13
0x5339c59f
#14
markGameAsLost
#15
setData
#6
0x6a08173c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1ecee167…9364
0x188d58…ea8e
2 touches
0 conflicts
0x1ecee167…9365
0x188d58…ea8e
2 touches
0 conflicts
0xc3006de0…9726
0x188d58…ea8e
2 touches
0 conflicts
0xc3006de0…9727
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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:
0x681e908b…e1ae09
1 conflict on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity