pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,396,672
← previous block
next block →
recent activity
Analyzing
Block #73,396,672
12 transactions · 8 stateful · 2026-05-09 05:43:44 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,396,672
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xff401d8f
· blocks 2
#3
0xb264ae19
#4
0x5bf9264c
#5
updateDataFeedsValuesPartial
#7
0x69feca08
#8
0xeffdedb0
#9
setData
#10
0x39435dac
#11
jMMeC
#2
0x719d975a
· blocks 1
#6
0x62be7533
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xa7fe0d97…ae1c
0x2a68ba…90c5
6 touches
3 conflicts
0x2101e15b…ba9a
0x065c9d…c394
6 touches
3 conflicts
0x8876d94c…8435
0x2a68ba…90c5
2 touches
0 conflicts
0x264c6e4e…cbb6
0x3bd359…433a
2 touches
0 conflicts
0xa980598e…ec52
0x3bd359…433a
2 touches
0 conflicts
0xcb643582…2626
0x3bd359…433a
2 touches
0 conflicts
0x110738b1…ed0c
0x754704…b603
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:
0x754704bc…afb603
3 conflicts on slot
0xa1087a5ca6…0a66c4
Audit this contract →
← previous block
·
next block →
recent activity