pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,501,466
← previous block
next block →
recent activity
Analyzing
Block #72,501,466
14 transactions · 12 stateful · 2026-05-05 02:23:00 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,501,466
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0x0c7abd22
· blocks 1
#3
updatePrices
#4
0x5bf9264c
#5
handleOps
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x323fe4ce
#10
forward
#11
0x69f954fc
#12
setData
#13
0x39435dac
#9
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x880d7867…68a4
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc267604b…025d
0x065c9d…c394
3 touches
1 conflict
0x04916f7b…b478
0x065c9d…c394
3 touches
1 conflict
0x5c8c6ab6…dc36
0x065c9d…c394
2 touches
0 conflicts
0x7354cf3a…f270
0x065c9d…c394
2 touches
0 conflicts
0xa130667b…3954
0x065c9d…c394
2 touches
0 conflicts
0xffe431af…8faa
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x880d7867cf…2668a4
Audit this contract →
← previous block
·
next block →
recent activity