pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,476,264
← previous block
next block →
recent activity
Analyzing
Block #73,476,264
10 transactions · 8 stateful · 2026-05-09 14:33:24 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,476,264
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x16040cc9
· blocks 2
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x69ff462c
#7
0x11789f…f556
#8
0x60b797…5f72
#9
0x39435dac
#2
0x16040cc9
· blocks 1
#3
0x16040cc9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d1acd7c…f345
0x5e1b1a…7777
6 touches
3 conflicts
0x5593214e…dfc1
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0x75c3ab…4f0d
6 touches
3 conflicts
0x00000000…0001
0x75c3ab…4f0d
6 touches
3 conflicts
0x00000000…0003
0x75c3ab…4f0d
6 touches
3 conflicts
0x97b0b2ee…4666
0x34b655…2a6f
2 touches
0 conflicts
0xa15427f6…d932
0x34b655…2a6f
2 touches
0 conflicts
0xa92c8763…6d7f
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:
0x5e1b1a14…587777
3 conflicts on slot
0x4d1acd7cf0…b2f345
Audit this contract →
← previous block
·
next block →
recent activity