pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,578,912
← previous block
next block →
recent activity
Analyzing
Block #73,578,912
10 transactions · 9 stateful · 2026-05-10 01:55:43 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,578,912
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x39435dac
#3
0x121eab2f
· blocks 1
#4
setData
#6
forward
#7
forward
#8
updateDataFeedsValuesPartial
#9
0x39435dac
#5
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16724e0f…803a
0x065c9d…c394
4 touches
1 conflict
0x244ee2e5…400c
0x065c9d…c394
4 touches
1 conflict
0xa93afc14…80c2
0x065c9d…c394
4 touches
1 conflict
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc1382d44…21d7
0x065c9d…c394
3 touches
1 conflict
0x1a3afbae…df9d
0x065c9d…c394
3 touches
1 conflict
0x5b6af007…0f35
0x34b655…2a6f
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x16724e0f63…75803a
Audit this contract →
← previous block
·
next block →
recent activity