pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,660,696
← previous block
next block →
recent activity
Analyzing
Block #73,660,696
13 transactions · 8 stateful · 2026-05-10 11:03:14 UTC
Parallelism
77
/100
Blocked
25
%
Avg conflicts / tx
0.23
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,660,696
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute
#2
0xcf7468f4
#3
removeLiquidity
#4
0x0c7abd22
· blocks 2
#5
0x1be2fb9c
#6
0x5bf9264c
#7
updateDataFeedsValuesPartial
#9
0x62be7533
#11
setData
#12
jMMeC
#8
0x0c7abd22
· blocks 1
#10
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
8
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a216773…3744
0xd32edf…ff58
5 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x7f975651…8c28
0x0555e3…2b9c
2 touches
0 conflicts
0x846f2172…fd54
0x0555e3…2b9c
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x24c5be9f…0075
0x065c9d…c394
2 touches
0 conflicts
0x29bd78c7…0daa
0x065c9d…c394
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:
0xd32edf66…9fff58
3 conflicts on slot
0x3a21677377…a33744
Audit this contract →
← previous block
·
next block →
recent activity