pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,336,457
← previous block
next block →
recent activity
Analyzing
Block #73,336,457
8 transactions · 7 stateful · 2026-05-08 23:03:07 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,336,457
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x121eab2f
· blocks 1
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
0x5339c59f
· blocks 1
#6
setData
#7
0x284bd8…584e
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x6f08361d…bda6
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3b2ea460…30d3
0x065c9d…c394
2 touches
0 conflicts
0x6745bc83…04c4
0x065c9d…c394
2 touches
0 conflicts
0x910998ee…3056
0x065c9d…c394
2 touches
0 conflicts
0x96fa0558…db86
0x065c9d…c394
2 touches
0 conflicts
0xb8dfa160…470c
0x065c9d…c394
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
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity