pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,979,258
← previous block
next block →
recent activity
Analyzing
Block #73,979,258
8 transactions · 8 stateful · 2026-05-11 22:37:45 UTC
Parallelism
63
/100
Blocked
25
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,979,258
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
withdraw
#2
0x0c7abd22
· blocks 2
#3
updateDataFeedsValuesPartial
#6
0x6a025ab0
#7
setData
#4
0x5339c59f
· blocks 1
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f08361d…bda6
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0b390c61…dc07
0x065c9d…c394
2 touches
0 conflicts
0x2da4bf39…8802
0x065c9d…c394
2 touches
0 conflicts
0x575effc5…db85
0x065c9d…c394
2 touches
0 conflicts
0x92756097…c88e
0x065c9d…c394
2 touches
0 conflicts
0xe86314ed…685c
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
3 conflicts on slot
0x6f08361da9…89bda6
Audit this contract →
← previous block
·
next block →
recent activity