pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,374,101
← previous block
next block →
recent activity
Analyzing
Block #73,374,101
11 transactions · 11 stateful · 2026-05-09 03:13:33 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,374,101
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
#2
0x121eab2f
· blocks 1
#4
0x1a945f9c
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
deposit
#8
0x69fea6d4
#9
setData
#10
approve
#3
0x121eab2f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6060de18…3272
0x065c9d…c394
4 touches
1 conflict
0x7965d47e…ab24
0x065c9d…c394
4 touches
1 conflict
0x85212464…49f3
0x065c9d…c394
4 touches
1 conflict
0xa2baf390…e732
0x065c9d…c394
4 touches
1 conflict
0xa545ca59…a593
0x065c9d…c394
4 touches
1 conflict
0xb9b57044…c8c2
0x065c9d…c394
4 touches
1 conflict
0xbb2c5707…3ffd
0x065c9d…c394
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:
0x065c9d28…a9c394
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity