pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,503,342
← previous block
next block →
recent activity
Analyzing
Block #73,503,342
8 transactions · 6 stateful · 2026-05-09 17:33:42 UTC
Parallelism
63
/100
Blocked
33
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,503,342
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#2
updatePrices
#3
updateDataFeedsValuesPartial
#6
0xed82b078
#7
setData
#4
0x5339c59f
· blocks 1
#5
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1fec95ff…d032
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xa1fdef94…cb87
0x065c9d…c394
3 touches
1 conflict
0x73c85761…4023
0x065c9d…c394
2 touches
0 conflicts
0x79ba9346…6152
0x065c9d…c394
2 touches
0 conflicts
0xab46888f…40f1
0x065c9d…c394
2 touches
0 conflicts
0xbf83d169…fdc1
0x065c9d…c394
2 touches
0 conflicts
0xc5f38257…41ae
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
0x1fec95ff53…3dd032
Audit this contract →
← previous block
·
next block →
recent activity