pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,651,937
← previous block
next block →
recent activity
Analyzing
Block #73,651,937
9 transactions · 6 stateful · 2026-05-10 10:04:10 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,651,937
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x39435dac
· blocks 1
#3
0xccf50a51
#4
updateDataFeedsValuesPartial
#5
0x9e76c652
#6
0x6a005892
#7
setData
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38524fae…9deb
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…0006
0x2ab50b…5c41
2 touches
0 conflicts
0x009d6d22…538c
0x2ab50b…5c41
2 touches
0 conflicts
0x069400f2…c518
0x2ab50b…5c41
2 touches
0 conflicts
0x0ec8c3d9…2f38
0x2ab50b…5c41
2 touches
0 conflicts
0x1199db9e…5fb5
0x2ab50b…5c41
2 touches
0 conflicts
0x2877f440…c2c8
0x34b655…2a6f
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
0x38524faed4…ae9deb
Audit this contract →
← previous block
·
next block →
recent activity