pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,753,209
← previous block
next block →
recent activity
Analyzing
Block #73,753,209
11 transactions · 9 stateful · 2026-05-10 21:27:33 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,753,209
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x39ecce49
#2
updatePrices
· blocks 2
#5
handleOps
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x6a00f8bd
#9
setData
#10
0xdca88b…2187
#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
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x1396e18f…c56b
0x39b9e0…7777
2 touches
0 conflicts
0xd352f775…a505
0x39b9e0…7777
2 touches
0 conflicts
0xfcdba3b0…cfc2
0x3bd359…433a
2 touches
0 conflicts
0x33a26eb2…2df0
0x5ff137…2789
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