pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,204,619
← previous block
next block →
recent activity
Analyzing
Block #73,204,619
10 transactions · 9 stateful · 2026-05-08 08:26:04 UTC
Parallelism
70
/100
Blocked
33
%
Avg conflicts / tx
0.5
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,204,619
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x4500f50f
· blocks 3
#3
updatePrices
#5
updateDataFeedsValuesPartial
#7
0xeffdedb0
#8
setData
#9
0x69fd9e94
#2
0x76368669
· blocks 2
#4
0x121eab2f
#6
0x62be7533
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x70b2f813…783c
0x2a68ba…90c5
6 touches
3 conflicts
0xce7bfe5e…5e58
0x065c9d…c394
4 touches
1 conflict
0x481d2d32…90d6
0x065c9d…c394
3 touches
1 conflict
0x60b24061…7c25
0x188d58…ea8e
2 touches
0 conflicts
0x9413ddeb…70dd
0x188d58…ea8e
2 touches
0 conflicts
0xe75ce681…ba5f
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:
0x754704bc…afb603
3 conflicts on slot
0x17606ba612…ea1b6e
Audit this contract →
← previous block
·
next block →
recent activity