pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,664,028
← previous block
next block →
recent activity
Analyzing
Block #73,664,028
10 transactions · 10 stateful · 2026-05-10 11:25:41 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,664,028
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x121eab2f
#3
0x98717539
· blocks 1
#4
0x785f5745
#5
updateDataFeedsValuesPartial
#6
0x6a006bac
#7
setData
#8
0x0c7abd22
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38524fae…9deb
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x3bfa194d…882e
0x065c9d…c394
2 touches
0 conflicts
0x3ee8a7d5…d2cb
0x065c9d…c394
2 touches
0 conflicts
0x737ffcea…17e8
0x065c9d…c394
2 touches
0 conflicts
0x7f81fb82…633e
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:
0x34b6552d…112a6f
1 conflict on slot
0x38524faed4…ae9deb
Audit this contract →
← previous block
·
next block →
recent activity