pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,382,896
← previous block
next block →
recent activity
Analyzing
Block #73,382,896
8 transactions · 7 stateful · 2026-05-09 04:12:01 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,382,896
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xbbb036a8
· blocks 1
#3
0x39435dac
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0xeffdedb0
#7
setData
#2
0x575c0012
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd70bea3…1ffe
0x3bd359…433a
4 touches
1 conflict
0x2b9c6652…d14e
0x754704…b603
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
2 touches
0 conflicts
0x1c840894…764a
0x34b655…2a6f
2 touches
0 conflicts
0x7b1d1371…271c
0x34b655…2a6f
2 touches
0 conflicts
0xaf59eb33…be7d
0x34b655…2a6f
2 touches
0 conflicts
0xd895ee0b…d301
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:
0x3bd359c1…15433a
1 conflict on slot
0xdd70bea3b0…701ffe
Audit this contract →
← previous block
·
next block →
recent activity