pev
.
One block, wave by wave
→
analytics
docs
offline
by Silk Nodes →
pev
/
block
/
#73,480,610
← previous block
next block →
recent activity
Analyzing
Block #73,480,610
10 transactions · 9 stateful · 2026-05-09 15:02:18 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,480,610
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
updateDataFeedsValuesPartial
#3
0x69ff4cf1
#4
setData
#5
0x121eab2f
#6
0x98717539
· blocks 1
#8
0x0c7abd22
#9
forward
#7
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafd59af5…5257
0xc8689a…ee79
4 touches
1 conflict
0x664bf99e…0a8c
0x34b655…2a6f
4 touches
1 conflict
0x6b25903b…05ab
0x34b655…2a6f
4 touches
1 conflict
0x6f3e0355…3bce
0x34b655…2a6f
4 touches
1 conflict
0x7cb2f3fa…4836
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xaf498679…7732
0x34b655…2a6f
4 touches
1 conflict
0xcd5c7f64…ad4b
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:
0xc8689a47…62ee79
1 conflict on slot
0xafd59af545…b35257
Audit this contract →
← previous block
·
next block →
recent activity