pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,484,098
← previous block
next block →
recent activity
Analyzing
Block #73,484,098
9 transactions · 7 stateful · 2026-05-09 15:25:30 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,484,098
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
setData
#5
0x0c7abd22
· blocks 1
#7
0x69ff5262
#8
0x39435dac
#6
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb45d9d6…cb80
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0xb8f02370…7bb0
0xd32edf…ff58
3 touches
1 conflict
0x866bf367…7a60
0x188d58…ea8e
2 touches
0 conflicts
0x866bf367…7a62
0x188d58…ea8e
2 touches
0 conflicts
0x866bf367…7a63
0x188d58…ea8e
2 touches
0 conflicts
0x9ff75095…6014
0x188d58…ea8e
2 touches
0 conflicts
0x9ff75095…6015
0x188d58…ea8e
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
0xcb45d9d62a…b1cb80
Audit this contract →
← previous block
·
next block →
recent activity