pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,338,221
← previous block
next block →
recent activity
Analyzing
Block #73,338,221
10 transactions · 9 stateful · 2026-05-08 23:14:53 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,338,221
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69fe6ee4
· blocks 1
#3
0x69fe6ee5
#4
updatePrices
#5
0x39435dac
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0xeffdedb0
#9
setData
#2
0x69fe6ee5
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1eb862eb…6c91
0x34b655…2a6f
2 touches
0 conflicts
0x2b855cdd…f64b
0x34b655…2a6f
2 touches
0 conflicts
0x5b6af007…0f35
0x34b655…2a6f
2 touches
0 conflicts
0x6cab9ef4…f849
0x34b655…2a6f
2 touches
0 conflicts
0xd895ee0b…d301
0x34b655…2a6f
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:
0x681e908b…e1ae09
1 conflict on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity