pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,395,968
← previous block
next block →
recent activity
Analyzing
Block #73,395,968
12 transactions · 10 stateful · 2026-05-09 05:39:01 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,395,968
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
updatePrices
#3
updatePrices
#5
0x98717539
#6
updateDataFeedsValuesPartial
#7
0x323fe4ce
#8
setData
#9
0xc5a04723
#10
0x69fec8ed
#11
0xeffdedb0
#4
0x121eab2f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0x09e7c751…e1f9
0x065c9d…c394
2 touches
0 conflicts
0x3bf36078…cac6
0x065c9d…c394
2 touches
0 conflicts
0x422f85e2…50f8
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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:
0x065c9d28…a9c394
1 conflict on slot
0x4d87512b00…43897c
Audit this contract →
← previous block
·
next block →
recent activity