pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,263,629
← previous block
next block →
recent activity
Analyzing
Block #73,263,629
8 transactions · 7 stateful · 2026-05-08 14:58:29 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,263,629
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x121eab2f
· blocks 1
#2
0xec2bd3f2
#3
updateDataFeedsValuesPartial
#4
setData
#6
0x69fdfa8d
#7
0xeffdedb0
#5
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x284f1de9…3525
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b390c61…dc07
0x065c9d…c394
4 touches
1 conflict
0x7681e14e…611f
0x065c9d…c394
2 touches
0 conflicts
0xbdff944d…447e
0x2a68ba…90c5
2 touches
0 conflicts
0x12711b58…80f3
0x384275…7777
2 touches
0 conflicts
0x1167512f…b162
0x3bd359…433a
2 touches
0 conflicts
0x2f1c865b…052a
0x3bd359…433a
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
0x284f1de9a1…7c3525
Audit this contract →
← previous block
·
next block →
recent activity