pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,348,609
← previous block
next block →
recent activity
Analyzing
Block #73,348,609
12 transactions · 10 stateful · 2026-05-09 00:23:59 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,348,609
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69fe7f17
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
0x98717539
#5
setData
#6
0x5339c59f
· blocks 1
#8
updateTemporalNumericValuesV1
#9
0x69fe7f17
#10
0xeffdedb0
#11
jMMeC
#7
0xed82b078
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
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1b9e654e…0a08
0x34b655…2a6f
2 touches
0 conflicts
0x23951077…539b
0x34b655…2a6f
2 touches
0 conflicts
0x6ddcb186…0578
0x34b655…2a6f
2 touches
0 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
2 touches
0 conflicts
0x908d4442…2c4b
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:
0x2a68ba18…8e90c5
1 conflict on slot
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity