pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,328,301
← previous block
next block →
recent activity
Analyzing
Block #73,328,301
9 transactions · 8 stateful · 2026-05-08 22:09:00 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,328,301
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
· blocks 1
#2
0x323fe4ce
#3
approve
#4
updateDataFeedsValuesPartial
#5
0x69fe5f74
#6
0xeffdedb0
#7
setData
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ea57326…329f
0x34b655…2a6f
4 touches
1 conflict
0xcbf04108…7fb4
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x0eac6378…36f4
0x34b655…2a6f
2 touches
0 conflicts
0x33f2d9b1…b689
0x34b655…2a6f
2 touches
0 conflicts
0xac206e47…ef7d
0x34b655…2a6f
2 touches
0 conflicts
0xb4cd11d8…ed6e
0x34b655…2a6f
2 touches
0 conflicts
0xba6a5167…f2b6
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:
0x34b6552d…112a6f
1 conflict on slot
0x9ea57326ca…60329f
Audit this contract →
← previous block
·
next block →
recent activity