pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,270,578
← previous block
next block →
recent activity
Analyzing
Block #73,270,578
8 transactions · 8 stateful · 2026-05-08 15:44:49 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,270,578
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69fe0568
· blocks 1
#3
0x121eab2f
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0xeffdedb0
#7
setData
#2
0x69fe0568
#4
0x121eab2f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd821ae10…fe17
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b390c61…dc07
0x065c9d…c394
4 touches
1 conflict
0x1e93be00…6db2
0x065c9d…c394
4 touches
1 conflict
0x2d430d12…0d25
0x065c9d…c394
4 touches
1 conflict
0x32bb6c76…b01a
0x065c9d…c394
4 touches
1 conflict
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0xfd2905c7…bb6c
0x065c9d…c394
4 touches
1 conflict
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:
0xc8689a47…62ee79
1 conflict on slot
0xd821ae106f…bcfe17
Audit this contract →
← previous block
·
next block →
recent activity