pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,492,382
← previous block
next block →
recent activity
Analyzing
Block #73,492,382
11 transactions · 10 stateful · 2026-05-09 16:20:45 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,492,382
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
modifyLiquidities
#5
forward
#6
0x5339c59f
· blocks 2
#9
setData
#10
0x69ff5f54
#7
0x5339c59f
· blocks 1
#8
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x8799b422…7fc1
0x065c9d…c394
2 touches
0 conflicts
0x22beb554…9f2a
0x188d58…ea8e
2 touches
0 conflicts
0xc11baecb…e7da
0x188d58…ea8e
2 touches
0 conflicts
0xe75ce681…ba62
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…000b
0x24f29b…4337
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:
0x2a68ba18…8e90c5
3 conflicts on slot
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity