pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,310,504
← previous block
next block →
recent activity
Analyzing
Block #74,310,504
14 transactions · 12 stateful · 2026-05-13 11:23:15 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,310,504
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xb264ae19
· blocks 1
#2
execute
#3
0xed82b078
#4
addLiquidity
#5
0x5bf9264c
#6
0x5bf9264c
#7
0x98717539
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#11
0x6a045f9a
#12
setData
#13
0x39435dac
#10
updatePosition
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81955a0a…29ee
0x6657d1…8ccc
4 touches
1 conflict
0xeeb8b7fc…24d6
0x6657d1…8ccc
4 touches
1 conflict
0x3923d7de…bb41
0x754704…b603
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x7b43f938…3650
0x000000…012a
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x4dd1db39…a994
0x188d58…ea8e
2 touches
0 conflicts
0x4dd1db39…a995
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:
0x6657d192…be8ccc
1 conflict on slot
0x81955a0a11…9a29ee
Audit this contract →
← previous block
·
next block →
recent activity