pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,641,397
← previous block
next block →
recent activity
Analyzing
Block #73,641,397
10 transactions · 10 stateful · 2026-05-10 08:53:12 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,641,397
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
0x5339c59f
· blocks 2
#5
0x5339c59f
#7
0x6a0047ef
#8
setData
#9
0x39435dac
#4
0x5339c59f
· blocks 1
#6
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x22e295f5…1bef
0x065c9d…c394
2 touches
0 conflicts
0x4d87512b…897c
0x065c9d…c394
2 touches
0 conflicts
0x6abb10c5…aa05
0x065c9d…c394
2 touches
0 conflicts
0x8a738fd6…685d
0x065c9d…c394
2 touches
0 conflicts
0xf9fe3c67…7bac
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
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity