pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,658,411
← previous block
next block →
recent activity
Analyzing
Block #73,658,411
8 transactions · 7 stateful · 2026-05-10 10:47:54 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,658,411
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
updatePrices
#3
matchAdvancedOrders
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x39435dac
· blocks 1
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x119d3f42…8e26
0x34b655…2a6f
4 touches
1 conflict
0x15d039e7…4bb6
0x34b655…2a6f
4 touches
1 conflict
0x4d3e58e0…a2d7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xef17b8cd…9511
0x34b655…2a6f
4 touches
1 conflict
0x3f17d2db…b7d4
0x369824…96c2
2 touches
0 conflicts
0x73df860a…ce66
0x369824…96c2
2 touches
0 conflicts
0xb2ebfc0e…ca12
0x369824…96c2
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:
0x34b6552d…112a6f
1 conflict on slot
0x119d3f4253…4b8e26
Audit this contract →
← previous block
·
next block →
recent activity