pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,214,673
← previous block
next block →
recent activity
Analyzing
Block #73,214,673
8 transactions · 7 stateful · 2026-05-08 09:32:53 UTC
Parallelism
63
/100
Blocked
29
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,214,673
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
commit
#3
0x5339c59f
· blocks 2
#6
0x69fdae3d
#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
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd7e37a9…9eb5
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0d622e34…0000
0x681e90…ae09
2 touches
0 conflicts
0x00000000…000b
0xdcc981…88e8
2 touches
0 conflicts
0x3bab3664…1925
0xe72d25…8be6
2 touches
0 conflicts
0xb2484ed3…5b6a
0xe72d25…8be6
2 touches
0 conflicts
0x09106a95…1467
0xeedfbc…f7dc
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
3 conflicts on slot
0xbd7e37a9b5…859eb5
Audit this contract →
← previous block
·
next block →
recent activity