pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,483,055
← previous block
next block →
recent activity
Analyzing
Block #73,483,055
10 transactions · 8 stateful · 2026-05-09 15:18:33 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,483,055
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x5339c59f
· blocks 2
#5
0x5339c59f
#8
0xed82b078
#9
setData
#6
0x5339c59f
· blocks 1
#7
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x73be8557…7403
0x065c9d…c394
2 touches
0 conflicts
0xa6f1181f…7c0e
0x065c9d…c394
2 touches
0 conflicts
0xb7ea3de5…af63
0x065c9d…c394
2 touches
0 conflicts
0xb926270f…4cd5
0x065c9d…c394
2 touches
0 conflicts
0xc0af0cb1…c349
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
3 conflicts on slot
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity