pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,653,969
← previous block
next block →
recent activity
Analyzing
Block #73,653,969
11 transactions · 8 stateful · 2026-05-10 10:17:54 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,653,969
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x6a005bca
#3
updatePrices
#4
0x39435dac
· blocks 1
#5
0x121eab2f
#7
updateDataFeedsValuesPartial
#8
withdraw
#9
0xed82b078
#10
setData
#6
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf2438038…5fa7
0x34b655…2a6f
4 touches
1 conflict
0x0eac6378…36f4
0x34b655…2a6f
4 touches
1 conflict
0x218e3595…b7ca
0x34b655…2a6f
4 touches
1 conflict
0x55bb8e74…fc2f
0x34b655…2a6f
4 touches
1 conflict
0x69bed3c2…6fd6
0x34b655…2a6f
4 touches
1 conflict
0xac206e47…ef7d
0x34b655…2a6f
4 touches
1 conflict
0x2b093939…9086
0x1b6862…e19c
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
0xea02471df2…601542
Audit this contract →
← previous block
·
next block →
recent activity