pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,981,255
← previous block
next block →
recent activity
Analyzing
Block #73,981,255
9 transactions · 6 stateful · 2026-05-11 22:51:11 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,981,255
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x6a025dd7
#4
0x6a025dd7
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x6a025dd7
#8
setData
#3
0x1ffa3c9b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0ddbfd1d…93dd
0x065c9d…c394
2 touches
0 conflicts
0x2e74b725…adbd
0x065c9d…c394
2 touches
0 conflicts
0x5b603d66…eb40
0x065c9d…c394
2 touches
0 conflicts
0x610cc3a1…dae5
0x065c9d…c394
2 touches
0 conflicts
0x7680ee17…7234
0x065c9d…c394
2 touches
0 conflicts
0x7e1c96e5…a8e5
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:
0x065c9d28…a9c394
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity