pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,358,842
← previous block
next block →
recent activity
Analyzing
Block #73,358,842
10 transactions · 7 stateful · 2026-05-09 01:32:00 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,358,842
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69fe8f08
#2
0x69fe8f08
#3
0x55e58ed0
· blocks 1
#5
0x1a945f9c
#6
withdraw
#7
0x69fe8f08
#8
0xeffdedb0
#9
setData
#4
0x121eab2f
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
0xbdff944d…447e
0x2a68ba…90c5
4 touches
1 conflict
0x9251c13d…7142
0x065c9d…c394
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x4d87512b…897c
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0007
0x09f880…ede0
2 touches
0 conflicts
0x00000000…000a
0x09f880…ede0
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x05fb607a…dc62
0x3bd359…433a
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:
0x2a68ba18…8e90c5
1 conflict on slot
0xbdff944d20…a2447e
Audit this contract →
← previous block
·
next block →
recent activity