pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,200,741
← previous block
next block →
recent activity
Analyzing
Block #73,200,741
11 transactions · 10 stateful · 2026-05-08 08:00:18 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,200,741
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x69fd988a
#2
updatePrices
· blocks 2
#5
updateDataFeedsValuesPartial
#6
updatePosition
#7
updateTemporalNumericValuesV1
#8
collect
#9
0xeffdedb0
#10
setData
#3
updatePrices
· blocks 1
#4
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x37e1be01…6f19
0x54cd53…9e7d
2 touches
0 conflicts
0xa27fa22d…7dca
0x54cd53…9e7d
2 touches
0 conflicts
0xd1a0adf6…6e55
0x54cd53…9e7d
2 touches
0 conflicts
0x04ed0798…79a4
0x6657d1…8ccc
2 touches
0 conflicts
0x11904f1e…448c
0x6657d1…8ccc
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:
0xab35264b…1cfa38
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity