pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,482,722
← previous block
next block →
recent activity
Analyzing
Block #73,482,722
9 transactions · 8 stateful · 2026-05-09 15:16:20 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,482,722
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
approve
#3
execute
· blocks 1
#5
execute
#6
forward
#7
updateDataFeedsValuesPartial
#8
setData
#4
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb02fe354…948e
0x1b6862…e19c
4 touches
1 conflict
0xb02fe354…948e
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x1f86a9…17ed
4 touches
1 conflict
0x00000000…0001
0x1f86a9…17ed
4 touches
1 conflict
0x866bf367…7a62
0x188d58…ea8e
2 touches
0 conflicts
0x38aa1898…fdf5
0x1b6862…e19c
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
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:
0x1b68626d…2de19c
1 conflict on slot
0xb02fe35466…fd948e
Audit this contract →
← previous block
·
next block →
recent activity