pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,041,967
← previous block
next block →
recent activity
Analyzing
Block #73,041,967
11 transactions · 9 stateful · 2026-05-07 14:23:49 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,041,967
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
· blocks 2
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
collect
#8
setData
#9
forward
#10
0xeffdedb0
#2
updatePrices
· blocks 1
#3
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd574ca…7ab1
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x6e76b18c…e15d
0x116e7d…d8f1
2 touches
0 conflicts
0x6e76b18c…e15e
0x116e7d…d8f1
2 touches
0 conflicts
0x692a4122…76b8
0x350035…7777
2 touches
0 conflicts
0x2f1c865b…052a
0x3bd359…433a
2 touches
0 conflicts
0xa472d565…9fe4
0x3bd359…433a
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:
0xd574cae5…037ab1
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity