pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,464,530
← previous block
next block →
recent activity
Analyzing
Block #73,464,530
10 transactions · 8 stateful · 2026-05-09 13:15:21 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,464,530
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
0x5bf9264c
#4
0x5bf9264c
#5
0x98717539
#6
0x765aeb4f
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x3a1da2…e44d
#2
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
2 touches
0 conflicts
0x176a8d88…fb6a
0x34b655…2a6f
2 touches
0 conflicts
0x287ee53a…cb49
0x34b655…2a6f
2 touches
0 conflicts
0x41629728…ee69
0x34b655…2a6f
2 touches
0 conflicts
0x4a2d94ef…38df
0x34b655…2a6f
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
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity