pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,688,834
← previous block
next block →
recent activity
Analyzing
Block #73,688,834
12 transactions · 10 stateful · 2026-05-10 14:13:12 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,688,834
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
aggregate3
#3
approve
#4
0x6df9e92b
· blocks 1
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
0x6a0092ef
#10
setData
#11
exactInputSingle
#5
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5593214e…dfc1
0x3bd359…433a
4 touches
1 conflict
0x44ad89ba…cf83
0x5e1b1a…7777
4 touches
1 conflict
0x4d1acd7c…f345
0x5e1b1a…7777
4 touches
1 conflict
0x00000000…0000
0x75c3ab…4f0d
4 touches
1 conflict
0x00000000…0001
0x75c3ab…4f0d
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x00000000…0004
0x5da0f5…e94e
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
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:
0x3bd359c1…15433a
1 conflict on slot
0x5593214e1a…b4dfc1
Audit this contract →
← previous block
·
next block →
recent activity