pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,383,808
← previous block
next block →
recent activity
Analyzing
Block #73,383,808
10 transactions · 10 stateful · 2026-05-09 04:18:06 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,383,808
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x39435dac
· blocks 2
#4
updateDataFeedsValuesPartial
#6
0xeffdedb0
#7
setData
#8
0x39435dac
#9
0x39435dac
#3
0x98717539
#5
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa91c899f…6ee3
0x34b655…2a6f
4 touches
1 conflict
0xb378025c…30cf
0x34b655…2a6f
4 touches
1 conflict
0xcfdbe862…6b0e
0x34b655…2a6f
4 touches
1 conflict
0xd0a6cde5…29cc
0x34b655…2a6f
4 touches
1 conflict
0x6eba5e7f…4b52
0x34b655…2a6f
4 touches
1 conflict
0xedb848fe…6534
0x34b655…2a6f
4 touches
1 conflict
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0xf853eb8e…4027
0x34b655…2a6f
4 touches
1 conflict
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
0xa91c899f02…fa6ee3
Audit this contract →
← previous block
·
next block →
recent activity