pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,648,046
← previous block
next block →
recent activity
Analyzing
Block #73,648,046
9 transactions · 8 stateful · 2026-05-10 09:38:01 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,648,046
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a005271
#2
updatePrices
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x121eab2f
· blocks 1
#7
setData
#8
0x39435dac
#3
updatePrices
#6
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x1db8bedc…3ca5
0x065c9d…c394
2 touches
0 conflicts
0x27e11b7e…b434
0x065c9d…c394
2 touches
0 conflicts
0x719bb1e1…bd5a
0x065c9d…c394
2 touches
0 conflicts
0x87e7fcdc…8efb
0x065c9d…c394
2 touches
0 conflicts
0xcb1ff1f9…e185
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:
0x065c9d28…a9c394
1 conflict on slot
0x22e295f5d8…ac1bef
Audit this contract →
← previous block
·
next block →
recent activity