pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,328,291
← previous block
next block →
recent activity
Analyzing
Block #73,328,291
10 transactions · 9 stateful · 2026-05-08 22:08:56 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,328,291
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
#3
0x98717539
· blocks 1
#5
bet
#6
updateDataFeedsValuesPartial
#7
0x69fe5f70
#8
0xeffdedb0
#9
setData
#4
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1b0
0x8d66a4…3095
4 touches
1 conflict
0x96504a63…52d2
0x8d66a4…3095
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x13326c3d…fc8d
0x065c9d…c394
2 touches
0 conflicts
0x32e9c14b…e832
0x065c9d…c394
2 touches
0 conflicts
0x94a2ee70…19d6
0x065c9d…c394
2 touches
0 conflicts
0x9fdcb845…0b04
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:
0x8d66a43f…113095
1 conflict on slot
0x8a35acfbc1…6bd1b0
Audit this contract →
← previous block
·
next block →
recent activity